Github user kwmonroe commented on the issue:
https://github.com/apache/bigtop/pull/341
Rev 42 contains this update and has been released to the edge channel in
the charm store:
https://jujucharms.com/zookeeper/42
Pending CI tests to move it through to stable.
---
Github user kwmonroe commented on the issue:
https://github.com/apache/bigtop/pull/341
+1, thx for the explanation @Pekkari. A quick deploy with this addition
lgtm.
---
Github user Pekkari commented on the issue:
https://github.com/apache/bigtop/pull/341
I'm trying to ease the case where you have several spaces, and zookeeper
was deployed in the wrong one. Nowadays, you can set the constraint in juju,
and force departure and rejoin, or you can set
Github user PikkuJose commented on the issue:
https://github.com/apache/bigtop/pull/341
I'm trying to ease the case where you have several spaces, and zookeeper
was deployed in the wrong one. Nowadays, you can set the constraint in juju,
and force departure and rejoin, or you can set
Github user kwmonroe commented on the issue:
https://github.com/apache/bigtop/pull/341
@Pekkari I don't understand what a `zkpeer.changed` handler buys us given
that we already run a `check_cluster` when peers join and depart. Am I missing
a case where a peer would change that is
