On Tue, May 1, 2012 at 8:42 PM, Daniel Nichter <dan...@percona.com> wrote:
> 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. Well if the master doesn't have the replication log enabled, the slave would likely fall through to the ERROR state, but I'm fine with the normal state being renamed OK. The finer grains might be useful, but that's an awful lot of ongoing changes to underlying table. I'm not sure what impact that would have. -Dave
_______________________________________________ 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
