Difference between revisions of "Database Table: clustermove inprogress"
From Dreamwidth Notes
Exor674Bot (Talk | contribs) (Robot: Updating: Format, rm. invalid header key) |
|||
| Line 1: | Line 1: | ||
| − | {{Database Table|name=clustermove_inprogress|table type=global|need desc=1}} | + | {{Database Table|name=clustermove_inprogress|description=this table is used to track the transitions of users between clusters.|table type=global|need desc=1}} |
This table is used by the [[ljbackup.pl|ljbackup]] and [[ljumover.pl|ljumover]] daemons to track the transitions of users between clusters. | This table is used by the [[ljbackup.pl|ljbackup]] and [[ljumover.pl|ljumover]] daemons to track the transitions of users between clusters. | ||
= Definition = | = Definition = | ||
Revision as of 04:28, 30 January 2010
"{{{repo}}}" is not in the list of possible values (dw-free, dw-nonfree) for this property."{{{repo}}}" is not in the list of possible values (dw-free, dw-nonfree) for this property. This is a global table. This table is used by the ljbackup and ljumover daemons to track the transitions of users between clusters.
Definition
CREATE TABLE clustermove_inprogress ( userid INT UNSIGNED NOT NULL, locktime INT UNSIGNED NOT NULL, dstclust SMALLINT UNSIGNED NOT NULL, moverhost INT UNSIGNED NOT NULL, moverport SMALLINT UNSIGNED NOT NULL, moverinstance CHAR(22) NOT NULL, # base64ed MD5 hash PRIMARY KEY (userid) )
moverinstance identifies an instance of the ljumover daemon.
Relationships
Outgoing
- Foreign key: userid to user.userid
