[SOLR-13369] TriLevelCompositeIdRoutingTest failure: same route prefix maped to multiple shards

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 03/Apr/19 23:48
• Updated: 02/Oct/19 17:25

Description

thetaphi's 8x jenkins job just identified a reproducing seed that causes TriLevelCompositeIdRoutingTest to fail after detecting 2 docs with matching route prefixes on different shards...

   [junit4]   2> NOTE: reproduce with: ant test  -Dtestcase=TriLevelCompositeIdRoutingTest -Dtests.method=test -Dtests.seed=A6B6F0104FE6018F -Dtests.multiplier=3 -Dtests.slow=true -Dtests.locale=sr-Latn -Dtests.timezone=Pacific/Tongatapu -Dtests.asserts=true -Dtests.file.encoding=US-ASCII
   [junit4] FAILURE 9.38s J0 | TriLevelCompositeIdRoutingTest.test <<<
   [junit4]    > Throwable #1: org.junit.ComparisonFailure: routePrefix app9/2!user32 found in multiple shards expected:<shard[3]> but was:<shard[2]>
   [junit4]    >        at __randomizedtesting.SeedInfo.seed([A6B6F0104FE6018F:2EE2CFCAE11A6C77]:0)
   [junit4]    >        at org.apache.solr.cloud.TriLevelCompositeIdRoutingTest.test(TriLevelCompositeIdRoutingTest.java:122)

It's possible this is just a bug I introduced in SOLR-13210 due to a missunderstanding in how routePrefixes that use a bit mask (ie: /2 in the assertion failure) are expected to work – but I thought i had that squared away based on shalin's feedback in SOLR-13210

Issue Links

• is related to: SOLR-13210 TriLevelCompositeIdRoutingTest makes no sense -- can never fail