Watches are not invalidated when the client looses connection with ZK cluster.

[niamster]

In the connect loop the client does not try to reset active watches.
This leads to stale view of the world if the client becomes isolated.
I would expect to receive an event to ensure that the business logic is aware of partitioning and could react accordingly.