Thanks for the response! My direct access to this zk cluster is
limited. I'll see about getting a copy of the logs to examine. I'll
also try to coordinate your experiment of creating a znode in each node
in turn and checking the cluster-wide view of that data. If we see a
situation where the
It sounds to me like a regression. We always had the properties format for
4lw, this (membership:) breaks that. I'd recommend fixing it in the next
3.5/3.6. ie. output the membership on a single line "membership: \n".
Should be a pretty simple change - anyone interested in taking it on?
Also
Thanks for bringing this up Shawn.
I also checked on my fork, netty-transport-native-epoll is the one actually
needed. But yeah, netty-all is overkill.
I created a jira:
https://issues.apache.org/jira/browse/ZOOKEEPER-3494
I will upload my PR soon.
Regards,
Norbert
On Fri, Aug 2, 2019 at 2:07 A
