[
https://issues.apache.org/jira/browse/CURATOR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700991#comment-16700991
]
ASF GitHub Bot commented on CURATOR-483:
----------------------------------------
Github user njhill commented on the issue:
https://github.com/apache/curator/pull/281
Great, thanks @cammckenzie @Randgalt. And I just noticed something odd
which may be contributing to the confusion ... at least for me right now the
commits on the Commits tab are showing in the opposite order to normal i.e.
oldest one at the top...
> 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)
