You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Henrik Nordvik (JIRA)" <ji...@apache.org> on 2016/08/09 11:13:20 UTC

[jira] [Updated] (CURATOR-341) create().orSetData() retries indefinitely if node exists

     [ https://issues.apache.org/jira/browse/CURATOR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henrik Nordvik updated CURATOR-341:
-----------------------------------
    Summary: create().orSetData() retries indefinitely if node exists  (was: create.orSetData() retries indefinitely if node exists)

> 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)