[
https://issues.apache.org/jira/browse/ACCUMULO-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620318#comment-13620318
]
Hudson commented on ACCUMULO-1233:
----------------------------------
Integrated in Accumulo-Trunk-Hadoop-2.0 #170 (See
[https://builds.apache.org/job/Accumulo-Trunk-Hadoop-2.0/170/])
ACCUMULO-1233 retry znode child scans (Revision 1463735)
Result = SUCCESS
ecn :
Files :
* /accumulo/trunk
* /accumulo/trunk/assemble
* /accumulo/trunk/core
* /accumulo/trunk/examples
* /accumulo/trunk/fate/src/main/java/org/apache/accumulo/fate/ZooStore.java
*
/accumulo/trunk/fate/src/main/java/org/apache/accumulo/fate/zookeeper/ZooSession.java
* /accumulo/trunk/server
*
/accumulo/trunk/server/src/main/java/org/apache/accumulo/server/util/MetadataTable.java
* /accumulo/trunk/src
> 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
