Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Fri, 2 Oct 2015 22:28:27 +0000 (UTC)
From: "Jordan Zimmerman (JIRA)" <jira@apache.org>
To: dev@curator.apache.org
Message-ID: <JIRA.12902021.1443740042000.14888.1443824907636@Atlassian.JIRA>
In-Reply-To: <JIRA.12902021.1443740042000@Atlassian.JIRA>
References: <JIRA.12902021.1443740042000@Atlassian.JIRA>
 <JIRA.12902021.1443740042310@arcas>
Subject: [jira] [Commented] (CURATOR-268) Curator client doesn't behave well
 when it loses connection: CRUD operation fail
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jordan Zimmerman commented on CURATOR-268:
------------------------------------------

https://github.com/apache/curator/pull/111

I checked this against your test by adding delete.quietly() and create.orSetData() and the test works.

> Curator client doesn't behave well when it loses connection: CRUD operation fail
> --------------------------------------------------------------------------------
>
>                 Key: CURATOR-268
>                 URL: https://issues.apache.org/jira/browse/CURATOR-268
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.7.1, 2.9.0
>            Reporter: Benjamin Jaton
>            Assignee: Jordan Zimmerman
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: TestCuratorSaveConnLoss.java
>
>
> I am doing a basic stress test :
> - a TestingServer that keeps restarting in one thread
> - a Curator client that keeps creating/deleting a node in another
> After a few seconds, ether the create or the delete fail:
> {code}Thu Oct 01 15:35:10 PDT 2015 - Node /test has successfully been removed.
> Thu Oct 01 15:35:10 PDT 2015 - Recreating /test
> Thu Oct 01 15:35:10 PDT 2015 - Restarting server...
> Thu Oct 01 15:35:14 PDT 2015 - Restarting server...
> Thu Oct 01 15:35:15 PDT 2015 - ERROR: node should be removed.
> Thu Oct 01 15:35:15 PDT 2015 - Data of node is: test
> Node has been mysteriously created...
> org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /test
> 	at org.apache.zookeeper.KeeperException.create(KeeperException.java:123)
> 	at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> 	at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:1209)
> 	at org.apache.curator.framework.imps.CreateBuilderImpl$11.call(CreateBuilderImpl.java:720)
> 	at org.apache.curator.framework.imps.CreateBuilderImpl$11.call(CreateBuilderImpl.java:703)
> 	at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
> 	at org.apache.curator.framework.imps.CreateBuilderImpl.pathInForeground(CreateBuilderImpl.java:700)
> 	at org.apache.curator.framework.imps.CreateBuilderImpl.protectedPathInForeground(CreateBuilderImpl.java:477)
> 	at org.apache.curator.framework.imps.CreateBuilderImpl.forPath(CreateBuilderImpl.java:467)
> 	at org.apache.curator.framework.imps.CreateBuilderImpl.forPath(CreateBuilderImpl.java:44)
> 	at TestCuratorSaveConnLoss$3.run(TestCuratorSaveConnLoss.java:87){code}
> The create shouldn't fail, we're within 5 seconds of the create and the connection timeout is 10 secs.
> This is surprising as this basic scenario is - AFAIK - the reason Curator exists in the first place.


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