[
https://issues.apache.org/jira/browse/SOLR-11469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-11469:
----------------------------
Attachment: SOLR-11469_incomplete_and_broken.patch
bq. I'm not really sure how to make this test work reliably? ... unless maybe
we manually add replicas with explicitly specified coreNodeName and force them
to be the leader????
FWIW, the attached {{SOLR-11469_incomplete_and_broken.patch}} attempts this,
but i ran into SOLR-11479 which currently makes this impossible.
> LeaderElectionContextKeyTest has flawed logic: 50% of the time it checks the
> wrong shard's elections
> ----------------------------------------------------------------------------------------------------
>
> Key: SOLR-11469
> URL: https://issues.apache.org/jira/browse/SOLR-11469
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Attachments: SOLR-11469.patch, SOLR-11469_incomplete_and_broken.patch
>
>
> LeaderElectionContextKeyTest is very flaky -- and on millers beastit reports
> it shows a suspiciously close to "50%" failure rate.
> Digging into the test i realized that it creates a 2 shard index, then picks
> "a leader" to kill (arbitrarily) and then asserts that the leader election
> nodes for *shard1* are affected ... so ~50% of the time it kills the shard2
> leader and then fails because it doesn't see an election in shard1.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
