On 4/22/2019 7:15 AM, Raveendra Yerraguntla wrote:
Should the collection APIs need to be used to create a replicas?
The answer to that is an emphatic yes. ALL changes to SolrCloud
collections should be handled through the Collections API.
If you are creating replicas any other way, such as
@eric Thanks for the reply. The upgrading process is in two phases. In the
initial phase brings the cluster using new solr version binaries. In the next
phase use the non-deprecated functionalities and make use of the new
functionalities
Let me explain the problem little different way.
Enviro
My first question would “why do you think this is important?”. The additional
burden a leader has is quite small and is only present when indexing. Leaders
have no role in processing queries.
So unless you have, say, on the order of 100 leaders on a single Solr instance
_and_ are indexing heavi
All,
We are upgrading from solr 5.4 to solr 7.6. In 5.4 each solr process based on
the core.properties (shard value assigned) will be joining as either leader or
replica based on the sequence of start.
By following the same procedure in 7.6 the initial leader node solr process is
replaced with l
