[
https://issues.apache.org/jira/browse/SOLR-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764072#comment-16764072
]
Hoss Man commented on SOLR-13237:
---------------------------------
Also interesting: beasting hasn't turned up many (any?) seeds that reproduce
(on any branch) _except_ when using {{-Dtests.nightly=true}} ... but the test
doesn't do anything dependent on TEST_NIGHTLY, (or use {{usually()}} or
{{atLeast()}}, etc...) making me suspect that maybe the compounding factor is
something chosen at the randomized index config level? perhaps something
realting to the codecs?
need to investigate more.
> 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.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
