You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2019/03/06 18:00:00 UTC
[jira] [Updated] (SOLR-13237) Not all types of index corruption
garuntee a leader will "give up its leadership"
[ https://issues.apache.org/jira/browse/SOLR-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-13237:
----------------------------
Summary: Not all types of index corruption garuntee a leader will "give up its leadership" (was: Not al types of index corruption garuntee a leader will "give up its leadership")
> Not all types of index corruption garuntee a leader will "give up its leadership"
> ---------------------------------------------------------------------------------
>
> Key: SOLR-13237
> URL: https://issues.apache.org/jira/browse/SOLR-13237
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Priority: Major
> Attachments: SOLR-13237_logging.patch, log-fail-5D803D4699663918.txt, log-fail-DEADBEEF.txt, log-pass-BEEFBEEF.txt, log-pass-FEEDBEEF.txt
>
>
> While investigating failures from LeaderTragicEventTest, I've found some reproducible situations where (externally introduced) index corruption can cause a leader to reject updates, but not automatically give up it's leadership.
> See discussion in LUCENE-8692 – notably simon's comment on why/how some things are explicitly not treated as tragic today for a disucssion of the root cause.
> *We may need/want to rethink & improve the situations where a leader gives up leadership, above and beyond IW registering a tragic exception*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org