[
https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888240#comment-13888240
]
Evaristo commented on CURATOR-72:
---------------------------------
Hi there,
TestListenerWithLeaderSelectorBis shows a snow ball effect with
ConnectionLossExceptions
One of the issues that I have found with CURATOR-72 code is that callBack for
retriesExhausted in background operations is called twice (once by
checkBackgroundRetry and another one by handleBackgroundOperationException).
This generates an snow fall effect if you are using for instance a guaranted
delete like is used by the leader selector to delete lock nodes when the
connection is suspended.
Even fixing that, I am pretty sure there is more issues because the
ConnectionLoss exceptions storm still grows
> Background operations don't wait for connection timeout
> -------------------------------------------------------
>
> Key: CURATOR-72
> URL: https://issues.apache.org/jira/browse/CURATOR-72
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 2.3.0
> Reporter: Evaristo Camarero
> Assignee: Jordan Zimmerman
> Fix For: 2.4.0
>
> Attachments: TestListener.java, TestListenerConnectedAtStart.java,
> TestListenerSequence.java, TestListenerWithLeaderSelector.java,
> TestListenerWithLeaderSelectorBis.java, test.java
>
>
> Background operations don't wait for the configured connection timeout before
> failing. Attached test shows the problem.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
