curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-341) create().orSetData() retries indefinitely if node exists
Date Tue, 09 Aug 2016 21:57:20 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414306#comment-15414306
] 

Cameron McKenzie commented on CURATOR-341:
------------------------------------------

Your assessment looks correct to me. Would you like to provide a PR with a unit test and a
fix? If not, I will fix it when I get a minute.

> create().orSetData() retries indefinitely if node exists
> --------------------------------------------------------
>
>                 Key: CURATOR-341
>                 URL: https://issues.apache.org/jira/browse/CURATOR-341
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 3.0.0
>            Reporter: Henrik Nordvik
>
> Symptom:
> One call to create.orSetData().inBackground(callback) writes the data to zookeeper infinitely
many times. Version numbers in stat increase quickly. Callback is also called multiple times.
> Added the following to TestFramework.testCreateOrSetData() to make it fail:
> {code}
> CuratorEvent event2 = queue.poll(new Timing().milliseconds(), TimeUnit.MILLISECONDS);
> Assert.assertNull(event2);
> {code}
> (slows down test, but just to demonstrate it)
> Seems like CreateBuilderImpl.backgroundSetData() shouldn't requeue mainOperation after
doing setData.
> {code}
> client.queueOperation(mainOperationAndData);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message