[ https://issues.apache.org/jira/browse/SOLR-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786106#comment-16786106 ]
ASF subversion and git services commented on SOLR-13237: -------------------------------------------------------- Commit e827dc22347f597a33c61ae4b4604354627efccf in lucene-solr's branch refs/heads/master from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=e827dc2 ] SOLR-13237: AwaitsFix LeaderTragicEventTest until we can make the underlying corruption detection reliable > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org