You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2017/11/27 20:43:00 UTC
[jira] [Created] (SOLR-11685)
CollectionsAPIDistributedZkTest.testCollectionsAPI fails regularly with
cluster state mismatch
Varun Thacker created SOLR-11685:
------------------------------------
Summary: CollectionsAPIDistributedZkTest.testCollectionsAPI fails regularly with cluster state mismatch
Key: SOLR-11685
URL: https://issues.apache.org/jira/browse/SOLR-11685
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Varun Thacker
I've been noticing lots of failures on Jenkins where the document add get's rejected because of leader conflict and throws an error like
{code}
ClusterState says we are the leader (https://127.0.0.1:38715/solr/awhollynewcollection_0_shard2_replica_n2), but locally we don't think so. Request came from null
{code}
Scanning Jenkins logs I see that these failures have increased since Sept 28th and has been failing daily.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org