[CURATOR-246] Parent task for adding a SESSION_LOST connection state, etc.

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Framework, Recipes
• Assignee: Unassigned
• Reporter: Dong Lei
• Created: 20/Aug/15 06:02
• Updated: 28/Dec/15 18:55
• Resolved: 28/Dec/15 18:55

Description

Spark now leverage curator to help manage the connections to ZK and do leader election.
Currently, whenever a ZK session gets disassociated, the ConnectionStateManager will be aware and mark the state to be SUSPENDED and a new leader election will be triggered.
Even though a ZK session is able to reconnect to another machine very soon.

I wonder if we can tolerate such unstable network trembling and do not trigger a leader election. Because the upper layer application's (like spark) reaction of new leader can be very costly.

Issue Links

• supercedes: CURATOR-185 Create a LOST_SESSION connection state

Sub-Tasks

• Extend Curator's connection state to support SESSION_LOST: Resolved
• Introduce pluggable error handlers: Resolved
• Update all Curator recipes to use new pluggable Error Handler: Closed