[jira] [Commented] (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:comment-tabpanel=16845569#comment-16845569 ] ASF subversion and git services commented on SOLR-13237: Commit fced8ab89e98c565166059e5052d3bc700468199 in lucene-solr's branch refs/heads/branch_7_7 from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=fced8ab ] SOLR-13237: AwaitsFix LeaderTragicEventTest until we can make the underlying corruption detection reliable (cherry picked from commit e827dc22347f597a33c61ae4b4604354627efccf) > 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
[jira] [Commented] (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:comment-tabpanel=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
[jira] [Commented] (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:comment-tabpanel=16786103#comment-16786103 ] ASF subversion and git services commented on SOLR-13237: Commit fe6df3e48524992bf9b95bc7a8cc5d857f322b49 in lucene-solr's branch refs/heads/branch_7x from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=fe6df3e ] SOLR-13237: AwaitsFix LeaderTragicEventTest until we can make the underlying corruption detection reliable (cherry picked from commit e827dc22347f597a33c61ae4b4604354627efccf) > 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
[jira] [Commented] (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:comment-tabpanel=16786104#comment-16786104 ] ASF subversion and git services commented on SOLR-13237: Commit af7765ba5db8a1e65770e22dbbbcda5a76db1be6 in lucene-solr's branch refs/heads/branch_8_0 from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=af7765b ] SOLR-13237: AwaitsFix LeaderTragicEventTest until we can make the underlying corruption detection reliable (cherry picked from commit e827dc22347f597a33c61ae4b4604354627efccf) > 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
[jira] [Commented] (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:comment-tabpanel=16786105#comment-16786105 ] ASF subversion and git services commented on SOLR-13237: Commit bb5b7f08b1b3bb22b0cb8549c446abe7e3a4f3ca in lucene-solr's branch refs/heads/branch_8x from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=bb5b7f0 ] SOLR-13237: AwaitsFix LeaderTragicEventTest until we can make the underlying corruption detection reliable (cherry picked from commit e827dc22347f597a33c61ae4b4604354627efccf) > 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
