You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the beginning, the execution will be failed, but when count larger than THRESHOLD, the execution will be successful. And the attempt execution and fall back will also be successful.
In the concurrent scenario, with Hystrix 1.5.12, the final state of the execution will keep successful all the time. But with Hystrix 1.5.13, the state will be fail since the state of circuit breaker is open.
The reason should be that the attempt execution will markNonSuccess() in Hystrix 1.5.13 and make the attempt execution cannot set the state of circuit breaker from HALF_OPEN into CLOSE.
The text was updated successfully, but these errors were encountered:
yanglifan
changed the title
The state of a CircuitBreaker will be still OPEN permanently
#Hystrix 1.5.13# The state of a CircuitBreaker will be still OPEN permanently
Sep 30, 2018
yanglifan
changed the title
#Hystrix 1.5.13# The state of a CircuitBreaker will be still OPEN permanently
[Hystrix 1.5.13] The state of a CircuitBreaker will be still OPEN permanently
Sep 30, 2018
The issue should be caused by pull #1621, and already mentioned by issue #1853.
I have demo this issue with a test.
At the beginning, the execution will be failed, but when
count
larger thanTHRESHOLD
, the execution will be successful. And the attempt execution and fall back will also be successful.In the concurrent scenario, with Hystrix 1.5.12, the final state of the execution will keep successful all the time. But with Hystrix 1.5.13, the state will be fail since the state of circuit breaker is open.
The reason should be that the attempt execution will
markNonSuccess()
in Hystrix 1.5.13 and make the attempt execution cannot set the state of circuit breaker from HALF_OPEN into CLOSE.The text was updated successfully, but these errors were encountered: