org.apache.solr.common.SolrException: No registered leader was found after waiting for 4000ms , collection: kla_collection slice: shard6

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via lucene-solr-user by Erick Erickson, 1 year ago
No registered leader was found after waiting for 4000ms , collection: kla_collection slice: shard6
via lucene-solr-user by Markus Jelsma, 1 year ago
No registered leader was found after waiting for 4000ms , collection: oi slice: shard3
via apache.org by Unknown author, 2 years ago
No registered leader was found after waiting for 4000ms , collection: XXXslice: shard9
via Apache's JIRA Issue Tracker by Piotr Tempes, 1 year ago
No registered leader was found after waiting for 4000ms , collection: testowa slice: shard1
via Stack Overflow by Debanjan Dhar
, 1 month ago
No registered leader was found after waiting for 4000ms , collection: X slice: shard118
via lucene-dev by Policeman Jenkins Server, 2 weeks ago
No registered leader was found after waiting for 1220000ms , collection: managed_coll slice: shard1 saw state=null with live_nodes=[]
org.apache.solr.common.SolrException: No registered leader was found after waiting for 4000ms , collection: kla_collection slice: shard6
at org.apache.solr.common.cloud.ZkStateReader.getLeaderRetry(ZkStateReader.java:568)
at org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:332)
at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:235)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.