[
https://issues.apache.org/jira/browse/SOLR-11469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214775#comment-16214775
]
Cao Manh Dat edited comment on SOLR-11469 at 10/23/17 7:44 AM:
---------------------------------------------------------------
Patch for this ticket. Beasted 150 times. The idea here is if will create two
collection with same sequence of requests ( no parallel ). We will have same
replica names for each collection. ( This satisfy current logic of
Assign.buildCoreNodeName )
was (Author: caomanhdat):
Patch for this ticket. The idea here is if will create two collection with same
sequence of requests ( no parallel ). We will have same replica names for each
collection. ( This satisfy current logic of Assign.buildCoreNodeName )
> 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.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]
