Dave, et al., Let's defined the slave IO thread status we want. Originally, you had proposed:
* running and initializing (INITIALIZING). This would likely replace RUNNING. * running and disconnected and will not attempt reconnect (DISCONNECTED) * running and awaiting reconnect (RECONNECTING) * running and connected normally (CONNECTED) * running but in some awful error state (ERROR) * thread has terminated normally (STOPPED) * etc. My only suggestion would be "OK" instead of "CONNECTED" because the thread could be connected but not actually working (for example, the replication log wasn't enabled on the master, or something else is happening on the master that prevents the slave from working). Alternatives to OK: RUNNING WORKING ACTIVE Or, if we're going to add even finer levels of status, like "READING FROM MASTER", "WRITING TO SLAVE QUEUE", etc., then perhaps "OK" is really something like "SLEEPING" (between reads on the master). Users will probably want this fine of a level of status since it amounts to a crude form of instrumentation if polled regularly. Also, it will probably come in handy if the slave gets stuck in some state like READING FROM MASTER. -Daniel _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
