In theory, each of the nodes uses the same configuration, right? So, in
theory, ANY of the nodes can do a DIH import. It is only way down low in the
update processing chain that an individual Solr input document needs to have
its key hashed and then the request is routed to the leader of the
appropriate shard.
In short, YOU decide whatever node that YOU want the DIH import to run on,
and Solr will automatically take care of actual distribution of individual
document update requests.
If you want to pick a leader node, fine, but there is no requirement or need
that you do so.
Scheduling is currently outside of the scope of Solr and SolrCloud.
-- Jack Krupansky
-----Original Message-----
From: kowish.adamosh
Sent: Sunday, July 14, 2013 8:42 AM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud leader
The problem is that I don't want to invoke data import on 8 server nodes but
to choose only one for scheduling. Of course if this server will shut down
then another one needs to take the scheduler role. I can see that there is
task for sheduling https://issues.apache.org/jira/browse/SOLR-2305 . I hope
they will take into account SolrCloud. And that's why I wanted to know if
current node is *currently* elected as the leader. The leader would be the
scheduler.
In the meanwhile, any ideas of how to solve data import scheduling on
SolrCloud architecture?
Kowish
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-leader-tp4077759p4077878.html
Sent from the Solr - User mailing list archive at Nabble.com.
