You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2009/05/27 05:51:46 UTC

[jira] Updated: (ZOOKEEPER-375) zoo_add_auth only retains most recent auth on re-sync

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

Mahadev konar updated ZOOKEEPER-375:
------------------------------------

    Attachment: ZOOKEEPER-375.patch

here's a patch that fixes the issue. not sure how to add a test for this. 

> zoo_add_auth only retains most recent auth on re-sync
> -----------------------------------------------------
>
>                 Key: ZOOKEEPER-375
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-375
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.1.0, 3.1.1
>            Reporter: Patrick Hunt
>            Assignee: Mahadev konar
>            Priority: Critical
>             Fix For: 3.2.0
>
>         Attachments: ZOOKEEPER-375.patch
>
>
> zoo_add_auth doesn't maintain a list of auths - it only stores the most recent auth send to the server. As a result on re-sync to the cluster it will lose (not reregister) any auths prior to the most recent.
> This code should maintain a list of auths similar to the java code. Be sure to free the memory in close.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.