SMU Classification: Restricted
Alright. Thanks
-Original Message-
From: Cee Tee
Sent: Saturday, September 28, 2019 3:24 PM
To: user@zookeeper.apache.org
Subject: Re: Zookeeper client with single address pointing to multiple servers
You would have to grab the config file from
You would have to grab the config file from the filesystem, or have some
process push it into a zookeeper node.
Hi Cee Tee,
I've check and this is working for 3.5.x but 3.4.x does not have the node.
Is there another way for 3.4.x?
On 28/9/19, 1:09 AM, "Cee Tee" wrote:
The latest config is available in node /zookeeper/config or via the config
command in the cli. If you want to know what
The latest config is available in node /zookeeper/config or via the config
command in the cli. If you want to know what servers are actually taking
requests you will have to go over them one by one issuing admin api server
stats calls.
On 27 September 2019 19:04:35 Shawn Heisey wrote:
On
On 9/27/2019 9:24 AM, Benjamin Reed wrote:
are you making the assumption that you have a single machine that will
always be up? that is not a common assumption these days, which is why
solr might be resistant to such a change.
you can have a single DNS name resolve to multiple IP addresses and
Thanks Ben. I'll continue to use the headless service which resolves to
multiple IP.
On 27/9/19, 11:24 PM, "Benjamin Reed" wrote:
are you making the assumption that you have a single machine that will
always be up? that is not a common assumption these days, which is why
solr
are you making the assumption that you have a single machine that will
always be up? that is not a common assumption these days, which is why
solr might be resistant to such a change.
you can have a single DNS name resolve to multiple IP addresses and
ZooKeeper client will use all those addresses
Thanks, I'm not sure whether Solr would make those change. I will ask them.
Any reason for this design?
On 27/9/19, 10:43 PM, "Cee Tee" wrote:
You could do that as follows:
1 Connect to a single always online entrypoint zookeeper of the zookeeper
cluster.
2 get Data the
You could do that as follows:
1 Connect to a single always online entrypoint zookeeper of the zookeeper
cluster.
2 get Data the config node at /zookeeper/config
3 parse it into a multinode connect string and reconnect using that string.
On 27 September 2019 16:33:48 LEE Ween Jiann
wrote:
