Difference between revisions of "Database Table: clustermove inprogress"
From Dreamwidth Notes
Exor674Bot (Talk | contribs) (Robot: Updating: Format) |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{Database Table|name=clustermove_inprogress|description=this table is used to track the transitions of users between clusters.|table type=global|repo=dw-free}} |
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 = | ||
| Line 10: | Line 10: | ||
moverport SMALLINT UNSIGNED NOT NULL, | moverport SMALLINT UNSIGNED NOT NULL, | ||
moverinstance CHAR(22) NOT NULL, # base64ed MD5 hash | moverinstance CHAR(22) NOT NULL, # base64ed MD5 hash | ||
| + | |||
PRIMARY KEY (userid) | PRIMARY KEY (userid) | ||
) | ) | ||
Latest revision as of 16:02, 22 July 2010
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
