Migrate Solr Replicas
When you replace a host, migrating replicas on that host to the new host, instead of depending on failure recovery, can help ensure optimal performance.
Where possible, the Solr service routes requests to the proper host. Both ADDREPLICA and DELETEREPLICA Collections API calls can be sent to any host in the cluster. For more information on the Collections API, see Collections API in Apache Solr Reference Guide.
- For adding replicas, the
nodeparameter ensures the new replica is created on the intended host. If no host is specified, Solr selects a host with relatively fewer replicas.
- For deleting replicas, the request is routed to the host that hosts the replica to be deleted.
Adding replicas can be resource intensive. For best results, add replicas when the system is not under heavy load. For example, do not add replicas when heavy indexing is occurring or when MapReduceIndexerTool jobs are running.
Cloudera recommends using API calls to create and unload cores. Do not use the Cloudera Manager Admin Console or the Solr Admin UI for these tasks.
- Host names:
- Collection name:
- The original replica
email_shard1_replica1, which is on
- The new replica
email_shard1_replica2, which will be on
- The original replica
(Optional) If you want to add a replica to a particular node, review the contents of
live_nodesdirectory on ZooKeeper to find all nodes available to host replicas. Open the Solr Administration User interface, click Cloud, click Tree, and expand live_nodes.The Solr Administration User Interface, including live_nodes, might appear as follows:
- Add the new replica on
solr02.example.comusing the ADDREPLICA API call.
Verify that the replica creation succeeds and moves from recovery state to
You can check the replica status in the Cloud view, which can be found at a URL similar to:
Accessing this URI returns an XML document that contains content about replication progress. A snippet of the XML content might appear as follows:
... <str name="numFilesDownloaded">126</str> <str name="replication StartTime">Tue Jan 21 14:34:43 PST 2014</str> <str name="timeElapsed">457s</str> <str name="currentFile">4xt_Lucene41_0.pos</str> <str name="currentFileSize">975.17 MB</str> <str name="currentFileSizeDownloaded">545 MB</str> <str name="currentFileSizePercent">55.0</str> <str name="bytesDownloaded">8.16 GB</str> <str name="totalPercent">73.0</str> <str name="timeRemaining">166s</str> <str name="downloadSpeed">18.29 MB</str> ...
- Use the CLUSTERSTATUS API call to retrieve information about the cluster,
including current cluster
Review the returned information to find the correct replica to remove. An example of the JSON file might appear as follows:
- Delete the old replica on
solr01.example.comserver using the
The DELETEREPLICA call removes the