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 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
, 4 months ago
No registered leader was found after waiting for 4000ms , collection: X slice: shard118
via lucene-solr-user by Markus Jelsma, 1 year ago
No registered leader was found after waiting for 4000ms , collection: oi slice: shard3
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 apache.org by Unknown author, 2 years ago
No registered leader was found after waiting for 4000ms , collection: XXXslice: shard9
via lucene-dev by Policeman Jenkins Server, 3 months 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: testowa slice: shard1	at org.apache.solr.common.cloud.ZkStateReader.getLeaderRetry(ZkStateReader.java:609)	at org.apache.solr.common.cloud.ZkStateReader.getLeaderRetry(ZkStateReader.java:595)	at org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:308)	at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:224)	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522)	at java.util.concurrent.FutureTask.run(FutureTask.java:277)	at org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:229)