curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-483) Sequential PersistentNodes with protection don't resync after reconnection
Date Tue, 27 Nov 2018 21:32:00 GMT

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

ASF GitHub Bot commented on CURATOR-483:
----------------------------------------

Github user cammckenzie commented on the issue:

    https://github.com/apache/curator/pull/281
  
    Thanks for the fix @njhill 


> 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
>             Fix For: 4.1.0
>
>
> 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)

Mime
View raw message