Next Previous Contents

8. Miscellaneous tables

There are a few miscellaneous tables that the scheduler uses. These may or may not be useful to you.

8.1 admin

The admin table is used primarily for upgrading the scheduler. The upgrade script can query the table to see what the last version was.

mysql> desc admin;
+---------+---------------+------+-----+---------+-------+
| Field   | Type          | Null | Key | Default | Extra |
+---------+---------------+------+-----+---------+-------+
| version | char(128)     |      | PRI |         |       |
| time    | timestamp(14) | YES  |     | NULL    |       |
| notes   | char(255)     |      |     |         |       |
+---------+---------------+------+-----+---------+-------+

8.2 checkpoint

The checkpoint table is used to checkpoint the scheduler state. It could possibly be used for other checkpointing too...

The data of the checkpoint is the serialized form of the Scheduler object tree. This includes the Scheduler object itself, the SchedListener, and related data structures. You should be able to stop the scheduler at anytime and get back to the last checkpointed state. Care should be taken when upgrading the scheduler however, since the checkpointed data may be invalid due to changes in the object structure.

If you want to start with a fresh slate, the mauictl flush command will stop the scheduler and flush the checkpoint table (as long as there are no running jobs). So if this fails for some reason, you can always delete from checkpoint; from the MySQL client.

mysql> desc checkpoint;
+--------+--------------+------+-----+---------+-------+
| Field  | Type         | Null | Key | Default | Extra |
+--------+--------------+------+-----+---------+-------+
| obj_id | varchar(255) |      | PRI |         |       |
| data   | mediumblob   |      |     |         |       |
+--------+--------------+------+-----+---------+-------+


Next Previous Contents