[CURATOR-505] A circuit breaking ConnectionStateListener would be very helpful

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.1.0
• Fix Version/s: 4.2.0
• Component/s: Client, Framework, Recipes
• Assignee: Jordan Zimmerman
• Reporter: Jordan Zimmerman
• Created: 06/Feb/19 16:50
• Updated: 23/Jun/22 20:24
• Resolved: 13/Feb/19 15:53

Description

Create a circuit breaker style ConnectionStateListener. It would proxy any ConnectionStateListeners used by Curator recipe/classes such that when the connection is lost the circuit would open for a period of time and, while open, ignore any changes in state. After the time period expires the circuit would close and send whatever the current connection state is. This way, if the connection is going up/down/up/down/up/down, the application would only see the first down and then N ms later hopefully the connection is repaired and the application would only see the reconnection.

Issue Links

• is superceded by: CURATOR-533 Improve CURATOR-505 by making the CircuitBreaker instance shared
• relates to: CURATOR-504 Race conditions in LeaderLatch after reconnecting to ensemble
• relates to: CURATOR-644 CLONE - Race conditions in LeaderLatch after reconnecting to ensemble
• links to: GitHub Pull Request #304