[
https://issues.apache.org/jira/browse/CURATOR-505?focusedWorklogId=198168&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-198168
]
ASF GitHub Bot logged work on CURATOR-505:
------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Feb/19 15:46
Start Date: 13/Feb/19 15:46
Worklog Time Spent: 10m
Work Description: yuri-tceretian commented on issue #304: [CURATOR-505]
WIP - Circuit breaking connection state listener decorator
URL: https://github.com/apache/curator/pull/304#issuecomment-463249550
> I could make the CircuitBreaker itself configurable.
I think another circuit breaker would be better. Anyway, that's just an
idea. The current implementation of circuit breaker is a good one.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 198168)
Time Spent: 1.5h (was: 1h 20m)
> 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
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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)
