[
https://issues.apache.org/jira/browse/SOLR-12412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545831#comment-16545831
]
Hoss Man commented on SOLR-12412:
---------------------------------
Dat: in the past 7 days, LeaderTragicEventTest.testOtherReplicasAreNotActive
has failed 36.33% (222 / 611) of all jenkins runs, and
LeaderTragicEventTest.test has failed 21.28% (130 / 611).
In just the past 24 hours, we've seen a failure rate of 29.09% (16 / 55) for
both methods.
It seems that even after your most recent commit, these tests need significant
hardening to run even remotely close to reliably?
> Leader should give up leadership when IndexWriter.tragedy occur
> ---------------------------------------------------------------
>
> Key: SOLR-12412
> URL: https://issues.apache.org/jira/browse/SOLR-12412
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
> Attachments: SOLR-12412.patch, SOLR-12412.patch,
> jenkins-failure-2325.log
>
>
> When a leader meets some kind of unrecoverable exception (ie:
> CorruptedIndexException). The shard will go into the readable state and human
> has to intervene. In that case, it will be the best if the leader gives up
> its leadership and let other replicas become the leader.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
