Thanks Mate for the responses. Brings a lot of clarity to me. I was able to
get it working this time without downtime. Don't know what I did wrong the
last time though.
On Mon, 20 Jul 2020 at 12:57, Szalay-Bekő Máté
wrote:
> echo "stat" | nc localhost 2182Hi,
>
> I guess this is the part you
Hello,
Can you try to change your configs by not using 0.0.0.0 in the ZOO_SERVERS?
Using 0.0.0.0 is not a recommended config since 3.5. If the java process
can not bind (due to some virtual network issue) to the host provided in
it's config, then you can use the quorumListenOnAllIPs parameter.
echo "stat" | nc localhost 2182Hi,
I guess this is the part you are referring:
https://zookeeper.apache.org/doc/r3.5.8/zookeeperAdmin.html#Upgrading+existing+nonTLS+cluster
(your link was pointing to the 3.3.2 admin guide where this chapter was
missing)
> 1) When I set sslQuorum=true and
Currently our production is running with 3.5.5 and it will take time to
move to 3.6.1.
When I dig more into this it seems to be related to Netty protocol and it’s
limitation. The system is stable when I fail back to NIO and without SSL.
As soon as I turned on Netty we are seeing sessions getting
Hello,
can you reproduce the problem with the latest 3.5 version? I mean 3.5.8.
There were a few bugfixes recently that can help. e.g.:
https://issues.apache.org/jira/browse/ZOOKEEPER-3756
Also you can try to increase some timeout parameters, see
