[
https://issues.apache.org/jira/browse/ZOOKEEPER-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923002#action_12923002
]
Andrei Savu commented on ZOOKEEPER-670:
---------------------------------------
It seems like this is no longer an issue on the trunk (fixed by ZOOKEEPER-888).
I've run {{zk.py}} against the latest version and I see no segfault but
unfortunately on the 3.3 branch it still crashes.
> 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.4.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.
-
You can reply to this email to add a comment to the issue online.
