[jira] [Updated] (ZOOKEEPER-670) zkpython leading to segfault on zookeeper server restart

["Mahadev konar (JIRA)" <ji...@apache.org>]

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

Mahadev konar updated ZOOKEEPER-670:
------------------------------------

    Fix Version/s:     (was: 3.4.0)
                   3.5.0

not a blocker. Moving it out of 3.4 release.

> zkpython leading to segfault on zookeeper server restart
> --------------------------------------------------------
>
>                 Key: ZOOKEEPER-670
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-670
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: contrib-bindings
>    Affects Versions: 3.2.1, 3.2.2
>         Environment: CentOS w/ Python 2.4
>            Reporter: Lei Zhang
>            Assignee: Henry Robinson
>            Priority: Critical
>             Fix For: 3.5.0
>
>         Attachments: voyager.patch, zk.py
>
>
> Zookeeper client using zkpython segfaults on zookeeper server restart. It is reliably reproducible using the attached script zk.py.
> I'm able to stop segfault using the attached patch voyager.patch, but zkpython seems to have deeper issue on its use of watcher_dispatch - on zookeeper server restart, I see up to 6 invocation of watcher_dispatch while my script is simply sleeping in the main thread. This can't be right.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira