[
https://issues.apache.org/jira/browse/CURATOR-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762071#comment-16762071
]
Jonathan Halterman edited comment on CURATOR-505 at 2/6/19 8:04 PM:
--------------------------------------------------------------------
The thing I'm most interested to guard against is any flood ofÂ
connect/reconnect attempts. I'm not sure if that would be related to this
issue, but I imagine that could also be solved by backoff retries with jitter?
was (Author: jhalterman):
The thing I'm most interested to guard against is any flood of connection
attempts. I'm not sure if that would be related to this issue, but I imagine
that could also be solved by backoff retries with jitter?
> A circuit breaking ConnectionStateListener would be very helpful
> ----------------------------------------------------------------
>
> Key: CURATOR-505
> URL: https://issues.apache.org/jira/browse/CURATOR-505
> Project: Apache Curator
> Issue Type: New Feature
> Components: Client, Framework, Recipes
> Affects Versions: 4.1.0
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
