Comment 5 for bug 1073083

realstically this is won't fix, we're migrating to juju-core and we'll have
a plan in place for prod pyju migration. The underlying issue is buried in
libzookeeper and the upstream basically treats it as a second class
citizen. There are dozens of extant patches for libzk and the python
bindings that fix real world issues, sadly none directly on this, and gdb
and friends haven't proved effective in determining root cause. The
underlying libzk code here is pretty awful (same really applies to the java
code, google cyclomatic complexity and zookeeper)

On Wed, Sep 18, 2013 at 4:37 AM, Mark Ramm <
<email address hidden>> wrote:

> ** Changed in: juju
> Importance: Critical => Wishlist
>
> ** Changed in: txzookeeper
> Importance: High => Wishlist
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1073083
>
> Title:
> Non-responsive zookeeper leads to spinning agent and traceback
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1073083/+subscriptions
>