[jira] [Resolved] (CURATOR-56) DistributedQueue znode name grows on re-queue

["Jordan Zimmerman (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CURATOR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman resolved CURATOR-56.
-------------------------------------

    Resolution: Fixed

Wrong node name being used when re-queueing message. Fix pushed for next release.
                
> DistributedQueue znode name grows on re-queue
> ---------------------------------------------
>
>                 Key: CURATOR-56
>                 URL: https://issues.apache.org/jira/browse/CURATOR-56
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.2.0-incubating
>         Environment: Zookeeper server version 3.4.5
>            Reporter: Adarsh Bhat
>            Assignee: Jordan Zimmerman
>             Fix For: 2.3.0
>
>         Attachments: CURATOR-56-testcase.patch
>
>
> Create a DistributedQueue with a lockPath. If QueueConsumer.consumeMessage() throws an exception, the message gets re-queued. Every time this happens, the name of the queue item znode grows in length. After many iterations, node names get very large and the server stops accepting new client connections.
> During a re-queue, the new znode created uses the old znode path as the base, and the SEQUENTIAL flag is set. Zookeeper appends a sequence number to the old path (which already had a sequence number), leading to a longer name during each re-queue.

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