[04/12] git commit: Another edge case found by Evaristo. When the SUSPEND is set, a background sync is executed to detect LOST. If the ZK connection is reset while this command is processing an incorr

Another edge case found by Evaristo. When the SUSPEND is set, a background sync is executed to detect LOST. If the ZK connection is reset while this command is processing an incorrect LOST might get set. Instead, keep track of ZooKeeper instance reset. If there is a reset ignore the background

[06/12] git commit: Previous version was incorrectly re-using the instanceIndex. Need to use latest value

Previous version was incorrectly re-using the instanceIndex. Need to use latest value Project: http://git-wip-us.apache.org/repos/asf/curator/repo Commit: http://git-wip-us.apache.org/repos/asf/curator/commit/8fbe4b7d Tree: http://git-wip-us.apache.org/repos/asf/curator/tree/8fbe4b7d Diff:

[01/12] git commit: Background connection errors would go straight to LOST which is different than foreground connection errors. Changed so that background connection errors go to SUSPENDED first just

Updated Branches: refs/heads/master 09f04e9c9 - 0a82f4eaa Background connection errors would go straight to LOST which is different than foreground connection errors. Changed so that background connection errors go to SUSPENDED first just like foreground connection errors. Project: