You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/11/03 03:38:00 UTC

[jira] [Commented] (CURATOR-483) Sequential PersistentNodes with protection don't resync after reconnection

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

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

GitHub user njhill opened a pull request:

    https://github.com/apache/curator/pull/281

    [CURATOR-483] Fix path used when re-creating sequential PersistentNode with protection

    Would previously result in creation of a second non-sequential znode.
    
    See https://issues.apache.org/jira/browse/CURATOR-483.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/njhill/curator CURATOR-483

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/281.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #281
    
----
commit 91e3a643ff6c562d30e75a61ed2d626befbcc40c
Author: nickhill <ni...@...>
Date:   2018-11-02T23:51:15Z

    fix path used when re-creating sequential PersistentNode with protection
    
    would previously result in creation of a second non-sequential znode

----


> 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)