The leader in the cluster is what is throwing the error.
One of the stack traces:
<http://lucene.472066.n3.nabble.com/file/n4201019/SolrError-Conflict.png>
However I didn't notice this one before which has a bit more info:
org.apache.solr.common.SolrException: Conflict
request:
http://<ip>:8080/solr/classic_bt/update?update.chain=savolangid&update.distrib=TOLEADER&distrib.from=http%3A%2F%2F<ip>%3A8080%2Fsolr%2Fclassic_bt%2F&wt=javabin&version=2
at
org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:241)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
We are using solr 4.10.2 and sadly our logging outside of the warn/error is
a little lackluster (I'm working on fixing it but need to work through a
change approval process).
--
View this message in context:
http://lucene.472066.n3.nabble.com/Has-anyone-seen-this-error-tp4200975p4201019.html
Sent from the Solr - User mailing list archive at Nabble.com.
