It kind of looks like the urls solrcloud is using are not accessible. When you go to the admin page and the cloud tab, can you access the urls it shows for each shard? That is, if you click on of the links or copy and paste the address into a web browser, does it work?
You may have to explicitly set the host= in solr.xml if it's not auto detecting the right one. Make sure the ports like right too. > waitForReplicasToComeUp > INFO: Waiting until we see more replicas up: total=2 found=1 > timeoutin=179999 That happens when you stop the cluster and try to start it again - before a leader is chosen, it will wait for all known replicas fora shard to come up so that everyone can sync up and have a chance to be the best leader. So at this point it was only finding one of 2 known replicas and waiting for the second to come up. After a couple minutes (configurable) it will just continue anyway without the missing replica (if it doesn't show up). - Mark On Dec 5, 2012, at 4:21 PM, Sudhakar Maddineni <maddineni...@gmail.com> wrote: > Hi, > We are uploading solr documents to the index in batches using 30 threads > and using ThreadPoolExecutor, LinkedBlockingQueue with max limit set to > 10000. > In the code, we are using HttpSolrServer and add(inputDoc) method to add > docx. > And, we have the following commit settings in solrconfig: > > <autoCommit> > <maxTime>300000</maxTime> > <maxDocs>10000</maxDocs> > <openSearcher>false</openSearcher> > </autoCommit> > > <autoSoftCommit> > <maxTime>1000</maxTime> > </autoSoftCommit> > > Cluster Details: > ---------------------------- > solr version - 4.0 > zookeeper version - 3.4.3 [zookeeper ensemble with 3 nodes] > numshards=2 , > 001, 002, 003 are the solr nodes and these three are behind the > loadbalancer <vip> > 001, 003 assigned to shard1; 002 assigned to shard2 > > > Logs:Getting the errors in the below sequence after uploading some docx: > ----------------------------------------------------------------------------------------------------------- > 003 > Dec 4, 2012 12:11:46 PM org.apache.solr.cloud.ShardLeaderElectionContext > waitForReplicasToComeUp > INFO: Waiting until we see more replicas up: total=2 found=1 > timeoutin=179999 > > 001 > Dec 4, 2012 12:12:59 PM > org.apache.solr.update.processor.DistributedUpdateProcessor > doDefensiveChecks > SEVERE: ClusterState says we are the leader, but locally we don't think so > > 003 > Dec 4, 2012 12:12:59 PM org.apache.solr.common.SolrException log > SEVERE: forwarding update to <001>:8080/solr/core1/ failed - retrying ... > > 001 > Dec 4, 2012 12:12:59 PM org.apache.solr.common.SolrException log > SEVERE: Error uploading: org.apache.solr.common.SolrException: Server at > <vip>/solr/core1. returned non ok status:503, message:Service Unavailable > at > org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:372) > at > org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:181) > 001 > Dec 4, 2012 12:25:45 PM org.apache.solr.common.SolrException log > SEVERE: Error while trying to recover. > core=core1:org.apache.solr.common.SolrException: We are not the leader > at > org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:401) > > 001 > Dec 4, 2012 12:44:38 PM org.apache.solr.common.SolrException log > SEVERE: Error uploading: org.apache.solr.client.solrj.SolrServerException: > IOException occured when talking to server at <vip>/solr/core1 > at > org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:413) > at > org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:181) > at > org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117) > at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:116) > ... 5 lines omitted ... > at java.lang.Thread.run(Unknown Source) > Caused by: java.net.SocketException: Connection reset > > > After sometime, all the three servers are going down. > > Appreciate, if someone could let us know what we are missing. > > Thx,Sudhakar.
