Solr has an excellent built-in replication feature that works perfectly in normal (non-distributed) Solr settings. However, when adding this feature to Solr cloud, I received an error telling that the /solr/copy handler could not be found (actually it does not appear in Solr output when Solr is started, although it is defined in solrconfig.xml ).
SolrWiki also points to a distributed update handler, but according to the author’s instructions, I know that it does not actually copy data, but only sends new documents to one of the nodes defined in config.
My question is:
>Why does the built-in Java-based replication not work in a distributed Solr setup? Is it a problem with the Solr cloud, a more basic problem or an error in my configuration (I checked everything many times, but still might be missing something)?
>What are other good ways to replicate in distributed Solr?
Answer your question directly;
> SolrCloud completes the replication setup and logic for you, you should let it do it yourself instead of introducing it into the mix “Manually” set up replication.> The point of SolrCloud is to hide the replication and sharing logic, allowing you to add more servers when available. You can of course create logically independent cloud clusters and indexes for both, but this is not required.< /p>
I am trying to add replication for each slave in Solr cloud to make the entire cluster more reliable. Our idea is to divide one The slices are distributed to multiple machines, even if one of the machines fails, the cluster can still work.
Solr has an excellent built-in replication feature that can be used in normal (non-distributed) Solr settings Works perfectly. However, when adding this feature to the Solr cloud, I received an error telling that the /solr/copy handler could not be found (actually it does not appear in the Solr output when Solr is started, although it is in solrconfig. xml).
SolrWiki also points to a distributed update handler, but according to the author’s instructions, I know that it does not actually copy data, but only sends new documents to one of the nodes defined in config.< /p>
My question is:
>Why does the built-in Java-based replication not work in a distributed Solr setup? Is it a problem with the Solr cloud, a more basic problem or an error in my configuration (I checked everything many times, but still might be missing something)?
>What are other good ways to replicate in distributed Solr?
Although I am a bit late to a party with an old question here; the answer is that Solr Cloud handles replication internally. The Solr Cloud wiki page explains this in detail If you have set numShards = 2 and add more servers (so there are four in total), the shard will be replicated to the new server-make sure your shard is on multiple nodes.
< p>Answer your question directly;
> SolrCloud completes the replication settings and logic for you, you should let it do it yourself, instead of introducing “manual” settings replication in the mix.> The focus of SolrCloud is to hide Copy and share logic, allowing you to add more servers when available. You can of course create logically independent cloud clusters and indexes for both, but this is not required.
p>