Why would "other nodes obviously won't be able to talk to this tmp node"? Can you elaborate?
Mark Miller-3 wrote > https://issues.apache.org/jira/browse/SOLR-4078 will be useful - that > should make it in 4.3. > > Until then, you want to get that node out, and you need the new node to be > assigned to the same shard. > > I guess I might try: > > Add your new node - explicitly tell it what shard to join by setting the > shard id. > > Start a new tmp node and set the host value to the old node that is gone. > This will work, though other nodes obviously won't be able to talk to this > tmp node - it will think it's the missing node though. Now send a core > unload command to it - that should cleanly remove it from the cluster. > Stop/remove the tmp node. > > > - Mark > > > On Feb 5, 2013, at 12:22 PM, Mike Schultz < > mike.schultz@ > > wrote: > >> Just to clarify, I want to be able to replace the down node with a host >> with >> a different name. If I were repairing that particular machine and >> replacing >> it, there would be no problem. But I don't have control over the name of >> my >> replacement machine. >> >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Adding-replacement-node-to-4-x-cluster-with-down-node-tp4038469p4038612.html >> Sent from the Solr - User mailing list archive at Nabble.com. -- View this message in context: http://lucene.472066.n3.nabble.com/Adding-replacement-node-to-4-x-cluster-with-down-node-tp4038469p4038925.html Sent from the Solr - User mailing list archive at Nabble.com.
