[
https://issues.apache.org/jira/browse/SOLR-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500943#comment-17500943
]
ASF subversion and git services commented on SOLR-16071:
--------------------------------------------------------
Commit 4687a53d46ec2593162d8fb85b8df7aa1d339dec in solr's branch
refs/heads/branch_9_0 from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=4687a53 ]
SOLR-16071: Fix occasional failure in DistributedQueryComponentCustomSortTest
(cherry picked from commit 7b9f4b9ed98635beeade94857cf59bf84302fe04)
> Occasional failure in DistributedQueryComponentCustomSortTest
> -------------------------------------------------------------
>
> Key: SOLR-16071
> URL: https://issues.apache.org/jira/browse/SOLR-16071
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
>
> IN SOLR-14758, a {{timeAllowed}} query was added to the end of
> DistributedQueryComponentCustomSortTest. The functionality of the test works,
> however it uses the {{setDistributedParams}} method for the query, which adds
> bogus servers to each of the shards in the param "shards=".
> Since timeAllowed is used, the query is cut off after 1 ms. The problem
> however is that the server does not have time to try all of the shards at
> that point. Therefore it will return an error if the correct shard URL is at
> the end of the list of shard servers.
> The easy solution here is merely to remove the {{setDistributedParams}} and
> not test that last query with bad shard servers. Or at least that's my best
> guess.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
