Ashok Kumar created SOLR-9402:
---------------------------------

             Summary: Isuses with SOLR and Zookeeper in production 
                 Key: SOLR-9402
                 URL: https://issues.apache.org/jira/browse/SOLR-9402
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
          Components: SolrCloud
    Affects Versions: 4.3.1
            Reporter: Ashok Kumar
            Priority: Critical


Getting below errors in the production during the business hours and leading to 
outage for hours and have to recycle the whole stack to resolve the issue.

ERROR - 2016-08-02 23:53:50.512; org.apache.solr.common.SolrException; shard 
update error StdNode: 
http://172.22.0.6:8984/solr/hpcalwin_shard1_replica1/:org.apache.solr.client.solrj.SolrServerException:
 IOException occured when talking to server at: 
http://172.22.0.6:8984/solr/hpcalwin_shard1_replica1

ERROR - 2016-08-03 10:43:27.232; org.apache.solr.common.SolrException; Sync 
request error: org.apache.solr.client.solrj.SolrServerException: Server refused 
connection at: http://172.22.0.6:8984/solr/hpcalwin_shard1_replica1

ERROR - 2016-08-08 09:55:52.506; org.apache.solr.common.SolrException; Error 
while trying to recover. 
core=hpcalwin_shard2_replica2:org.apache.solr.common.SolrException: No 
registered leader was found, collection:hpcalwin slice:shard2


ERROR – 2016-08-08 09:55:40.268; org.apache.solr.common.SolrException; 
org.apache.solr.common.SolrException: no servers hosting shard

ERROR - 2016-08-08 10:15:11.964; org.apache.solr.update.UpdateLog; Error 
inspecting tlog 
tlog{file=/PRD/ECM/DPE/solr-4.3.1/hpcalwin2/solr/hpcalwin_shard1_replica1/data/tlog/tlog.0000000000010476829
 refcount=2}

ERROR [LearnerHandler-/172.22.0.5:57448:LearnerHandler@562] - Unexpected 
exception causing shutdown while socket still open








--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to