I believe Arcadius has a point, but I still think the answer is no.
ZooKeeper clients (Solr/SolrJ) connect to a single ZooKeeper server
instance at a time, and keep that session open to that same server as long
as they can/need. During this time, all interactions between the client and
the ZK ense
Arcadius:
Note that one of the more recent changes is "per collection states" in
ZK. So rather
than have one huge clusterstate.json that gets passed out to to all
collection on any
change, the listeners can now listen only to specific collections.
Reduces the "thundering herd" problem.
Best,
Eri
Hello Shawn.
This question was raised because IMHO, apart from leader election, there
are other load-generating activities such as all 10 solrj
clients+solrCloudNodes listening to changes on clusterstate.json/state.json
and downloading the whole file in case there is a change... And this would
have
On 9/3/2015 9:47 PM, Arcadius Ahouansou wrote:
> Let's say we have 10 SolrJ clients all configured with
> zkhost=zk1:port,zk2:port,zk3:port
>
> For each of the 10 SolrJ clients, would it make a difference in term of
> load on zk1 (the server on the list) if we shuffle around the order of the
> ZK
Hello.
Let's say we have 10 SolrJ clients all configured with
zkhost=zk1:port,zk2:port,zk3:port
For each of the 10 SolrJ clients, would it make a difference in term of
load on zk1 (the server on the list) if we shuffle around the order of the
ZK servers in zkHost or is it all the same?
I would h
