You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Houston Putman (Jira)" <ji...@apache.org> on 2022/03/07 16:58:00 UTC

[jira] [Resolved] (SOLR-16071) Occasional failure in DistributedQueryComponentCustomSortTest

     [ https://issues.apache.org/jira/browse/SOLR-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Houston Putman resolved SOLR-16071.
-----------------------------------
    Fix Version/s: 9.0
       Resolution: Fixed

> 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
>             Fix For: 9.0
>
>
> 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: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org