[
https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889296#comment-13889296
]
Evaristo commented on CURATOR-72:
---------------------------------
The code is basically redundant with checkBackgroundRetry(operationAndData,
event). If you also maintain
handleBackgroundOperationException(operationAndData, e) you are for instance
calling twice the retriesExhausted callback. In some cases this has a snow ball
effect (e.g. guaranteed deletes grows exponentially because retries exhausted
callback generates a new background operation).
> 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, curator-72.patch, 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)
