[
https://issues.apache.org/jira/browse/CURATOR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700970#comment-16700970
]
ASF GitHub Bot commented on CURATOR-483:
----------------------------------------
Github user njhill commented on a diff in the pull request:
https://github.com/apache/curator/pull/281#discussion_r236832802
--- Diff:
curator-recipes/src/main/java/org/apache/curator/framework/recipes/nodes/PersistentNode.java
---
@@ -422,6 +422,9 @@ protected void deleteNode() throws Exception
}
}
+ // Hardcoded in {@link
org.apache.zookeeper.server.PrepRequestProcessor}
+ static final int SEQUENTIAL_SUFFIX_DIGITS = 10;
--- End diff --
@Randgalt I did so in the most recent commit (e.g. see the changes tab). On
the summary page github still shows the code as it was when the corresponding
comment was made.
> Sequential PersistentNodes with protection don't resync after reconnection
> --------------------------------------------------------------------------
>
> Key: CURATOR-483
> URL: https://issues.apache.org/jira/browse/CURATOR-483
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Affects Versions: 4.0.1
> Reporter: Nick Hill
> Priority: Major
>
> When using a {{PersistentNode}} with a sequential creation mode (in my case
> ephemeral but I think persistent would be the same) and "protection" turned
> on, unexpected duplicate znodes get created upon reconnection after a
> disconnect (without the sequence suffix), rather than it just taking
> ownership of the previously created znode.
> I tracked down the cause of this and have made a simple fix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
