Was it a test instance that you created 8983 is the default port, so possibly you started an instance before you had the ports setup properly, and it registered in zookeeper as a valid instance. You can use the Core API to UNLOAD it (if it is still running), if it isn't running anymore, I have yet to find a way to remove something from ZK.... We normally end up wiping zoo_data and bouncing everything at that point, instances should re-register themselves as they start up. But that is the sledgehammer to crack a walnut approach. :)
On 3 September 2013 13:55, Marc des Garets <m...@ttux.net> wrote: > Hi, > > I have setup SolrCloud with tomcat. I use solr 4.1. > > I have zookeeper running on 192.168.1.10. > A tomcat running solr_myidx on 192.168.1.10 on port 8080. > A tomcat running solr_myidx on 192.168.1.11 on port 8080. > > My solr.xml is like this: > <?xml version="1.0" encoding="UTF-8" ?> > <solr persistent="true" collection.configName="myidx"> > <cores adminPath="/admin/cores" defaultCoreName="collection1" > hostPort="8080" hostContext="solr_myidx" zkClientTimeout="20000"> > <core name="collection1" instanceDir="."/> > </cores> > </solr> > > I have tomcat starting with: -Dbootstrap_conf=true -DzkHost= > 192.168.1.10:2181 > > Both tomcat startup all good but when I go to the Cloud tab in the solr > admin, I see the following: > > collection1 --> shard1 --> 192.168.1.10:8983/solr > 192.168.1.11:8080/solr_ugc > 192.168.1.10:8080/solr_ugc > > I don't know what is 192.168.1.10:8983/solr doing there. Do you know how > I can remove it? > > It's causing the following error when I try to query the index: > SEVERE: Error while trying to recover. core=collection1:org.apache.** > solr.client.solrj.**SolrServerException: Server refused connection at: > http://192.168.10.206:8983/**solr <http://192.168.10.206:8983/solr> > > Thanks, > Marc >
