Hi,
I got the solution to the above problem . Sharing the code so that it could
help people in future
PoolingClientConnectionManager poolingClientConnectionManager = new
PoolingClientConnectionManager();
poolingClientConnectionManager.setMaxTotal(2);
Hi,
As per the suggestions above I shifted my focus to using CloudSolrServer. In
terms of sending updates to the leaders and reducing network traffic it
works great. But i faced one problem in using CloudSolrServer is that it
opens too many connections as large as five thousand connections. My
Update requests are routed only to leader nodes by CloudSolrServer so
there is a 1/numShards probability of avoiding an extra network hop.
It is *not* a 1/(number of nodes in cluster) probability as you may
think.
You may also be interested in
https://issues.apache.org/jira/browse/SOLR-4816 .
What Jack and Shalin said
Jack's comments about leaders changing is absolutely correct,
although practically they won't change all that often unless
you're bouncing nodes all over the place.
But as Shalin says, CloudSolrServer will already to this, at least
as far as sending updates to a
bq: Reason being If a write request is sent to the replica it
relays it to the leader and then the leader relays it to all the replicas.
This will help me in saving some network traffic as my application performs
continuous writes
How are you indexing? SolrJ already is leader aware and sends
Hi Erik,
I just wanted to clarify if u got my concern right. If i send some documents
to the replica core wont it first have to send the documents to the leader
core which in turn would be sending it back to the replica cores. If yes
then this will lead to additional network traffic which can be
There are three concepts to grasp:
1. You can send Solr update requests to ANY node of the cluster. Period.
2. Any extra network traffic (within the cluster) is likely to be negligible
and absolutely not worrying about unless you have definitive evidence to the
contrary.
3. Leader nodes in
Hi ,
I have a set up of 1 leader and 1 replica and I have a requirement where in
I need to find the leader core from the collection. Is there an api in solrj
by means of which this can be achieved.
--
View this message in context:
You can always query Zookeeper and find that information out.
Take a look at CloudSolrServer, maybe ZkCoreNodeProps etc.
for examples since CloudSolrServer is leader aware, it
should have some clues...
Or maybe ZkStateReader? I haven't been in that code much,
so I can't be more specific...
But
I have the same question. My purpose is to start the dih full process on
the leader and not on a replica.
I tried full import on a replica but watching logs it seemed to me that the
replica was loading data to send it to the leader which in turn has to
update all the replicas.
At least this is
Hi,
I have a requirement where in I want to write to the leader and read from
the replica. Reason being If a write request is sent to the replica it
relays it to the leader and then the leader relays it to all the replicas.
This will help me in saving some network traffic as my application
One option could be to get the clusterstate.json via the following Solr url
figure out the leader from the response json:
*
http://server:port/solr/zookeeper?detail=truepath=%2Fclusterstate.json*
On Wed, Jul 3, 2013 at 5:57 PM, vicky desai vicky.de...@germinait.comwrote:
Hi,
I have a
12 matches
Mail list logo
