[
https://issues.apache.org/jira/browse/SOLR-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138301#comment-15138301
]
ASF subversion and git services commented on SOLR-8658:
-------------------------------------------------------
Commit f4f1486895bf9cc18bb4e9f89a110c50ae63f59c in lucene-solr's branch
refs/heads/branch_5x from [~erickerickson]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f4f1486 ]
SOLR-8658: Fix test failure introduced in SOLR-8651
> Fix test failure introduced in SOLR-8651
> ----------------------------------------
>
> Key: SOLR-8658
> URL: https://issues.apache.org/jira/browse/SOLR-8658
> Project: Solr
> Issue Type: Bug
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Attachments: SOLR-8658.patch
>
>
> OK, I think I've found a possible reason. The waitForDocCount method waits
> until a response comes back with the, well, expected doc counts. But then it
> drops out of the wait loop the first time a query works.
> But then it goes out to each and every node and re-issues the request. This
> looks to be a 2-shard, 2-replica situation. So here's the theory: the second
> node hasn't yet opened a new searcher. So the wait loop is satisfied by, say,
> node2 but the test later looks at node4 (both for shard2) which hasn't
> completed opening a searcher yet so it fails.
> I could not get this to fail locally in 20 runs. So I'll beast the unchanged
> version some more to see but meanwhile commit this change which I think is
> more correct anyway and monitor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
