Handle slave failures

[sobrinho]

There is a lot of people requesting a way to handle slave failures.

Some questions:

1. What exactly defines a slave as failed?
2. In what moment we will mark the slave as down?
3. In what moment we will retry the failed slaves?
4. The application should boot and warn or raise when a slave is down? (Misconfiguration may not be detected if we allow the application to boot)

[drewB]

I am curious if there was any movement on this. Here are my answers to the questions asked:

1. When a no connection error is raised.
2. On the first no connection error.
3. For me I would say it should be a background process or perhaps not until a server restart.
4. Log an error. I don't like the idea of not allowing boot because on server restart that could be a big problem.