[ https://issues.apache.org/jira/browse/SOLR-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-13237: ---------------------------- Description: 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 was: 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. > Not al 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 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org