The list of destination servers can be dynamically changed in runtime,
see README there. Note that it supports "draining", but for that to work
the application needs to periodically willfully reconnect (very nice to
get Sysbench doing that). Same with adding new destinations - if
application connections are static it won't be able to use added nodes.

So if you write a notification script properly, you should be able to
manipulate glbd routing tables. The trick is when one of the nodes
crashes, somebody of the remaining has to report that. Also internally
glbd blacklists destination for a second if it can't connect to it. Does
not seem work that well though - connection attempt seems to introduce a
noticeable overhead (it is a heavy synchronous operation)

As for the overall state - I don't think it got tested enough. We
didn't have any feedback on it.

Regards,
Alex

On 2012-03-21 04:26, Vadim Tkachenko wrote: