On 1/26/2013 6:31 AM, Per Steffensen wrote:
We have actually tested this and found that the following will do it
* Shutdown all Solr nodes - make sure ZKs are still running
* For each replica (shard-instance) move its data-folder to the new
server (if they are not already available to it through some shared
storage)
* For each repilca (shard-instance) also move solr.xmls
* Extract clusterstate.json from ZK into a file. Modify that file so
that hosts/IPs and ports are correct according to new setup. Replace
clusterstate.json in ZK with the modified content of the
clusterstate.json file
* Start new Solr nodes
What I found is that you have to have the port correct in solr.xml.
That is what is used when populating the "live_nodes" structure in ZK.
When I first set up my little cloud, I changed the jetty port in
jetty.xml to 8985, but found that live_nodes was getting populated with
8983.
When I fixed jetty.xml to use the jetty.port system property (which is
also in my solr.xml), and set that property at startup, live_nodes in ZK
was correct with 8985 as the port.
Thanks,
Shawn
