You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2013/04/02 22:47:15 UTC
[jira] [Commented] (ACCUMULO-1233) race condition looking at
zookeeper nodes
[ https://issues.apache.org/jira/browse/ACCUMULO-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620256#comment-13620256 ]
Eric Newton commented on ACCUMULO-1233:
---------------------------------------
Running:
{noformat}
./bin/accumulo org.apache.accumulo.server.fate.Admin print
{noformat}
often fails with a NoNode exception during the random walk test.
> race condition looking at zookeeper nodes
> -----------------------------------------
>
> Key: ACCUMULO-1233
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1233
> Project: Accumulo
> Issue Type: Bug
> Components: master, tserver
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Minor
> Labels: 15_qa_bug
> Fix For: 1.5.0
>
>
> There's a common pattern used with zookeeper:
> {noformat}
> for (String child : zk.getChildren(path)) {
> byte[] content = zk.getData(path + "/" + child, null, null);
> doSomething(content);
> }
> {noformat}
> The problem is that between the getChildren() call and the getData() call, the child node has gone away.
> We'll typically retry these operations, but it puts big scary messages in the logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira