We could potentially have the following scenario:

1) A slave is specified with a slave delay (say an hour or so)
2) Bad data is written to master
3) The operator takes down the master, intending to prevent the bad data from being written to the slave
4) After the hour has elapsed, the slave applies the last batch of delayed operations it had read from the master before the master was taken offline

Do we want to do anything about this, or is it the operator's job to make sure the slave node is restarted in a scenario like this?