Hi Shawn, As suggested i gave the -Dhost=192.168.5.236 in command line for the server which was showing 127.0.0.1.
*./solr start -c -z 192.168.6.217:2181 <http://192.168.6.217:2181>,192.168.5.81:2181 <http://192.168.5.81:2181>,192.168.5.236:2181 <http://192.168.5.236:2181> -p 4567 -Dhost=192.168.5.236 -V* Now everything is good. Thank you so much. You may need to manually remove the 127.0.1.1 entries from zookeeper > after you fix the IP address problem. How to do that? With Regards Aman Tandon On Wed, Mar 11, 2015 at 8:02 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 3/11/2015 6:32 AM, Aman Tandon wrote: > > I restart my complete cluster but the problem still present. Please help. > > > > *Here is the screenshot url:* > > > > *http://i.imgur.com/QFdg89S.png > > > > http://i.imgur.com/tS0yTNh.png > > The first screenshot actually shows the problem, but it may not be > immediately obvious. In both cases where the shard leader is on > 127.0.1.1, recovery is not able to complete. > > The reason for this is extremely simple -- 127.0.1.1 is a loopback > address, not accessible remotely ... so when the machine at > 192.168.6.217 tries to contact the other machine, it is only talking to > itself, and is not able to find the leader to initiate recovery. > > I don't know why that machine chose to register itself in zookeeper > using a loopback address, unless perhaps the hosts file on that machine > is set up incorrectly so that the local hostname is associated with that > IP address. If you can't fix the IP lookup problem, you can override > the value that Solr uses with the "host" property, which you can set on > the java commandline (-Dhost=) or in the solr.xml file. > > http://wiki.apache.org/solr/SolrCloud#SolrCloud_Instance_Params > > You may need to manually remove the 127.0.1.1 entries from zookeeper > after you fix the IP address problem. > > Thanks, > Shawn > >
