You didn't really say much about what the failure *looks* like (in terms
of wether you get an assertion failure, if so where, and what the logs say
etc...) but I tried to run this test (with this seed) locally a few times
and skimmed the logs...
what i see is that some form of "time allowed exceeded" warning gets
logged, and then there are a bunch of (aparently inter-node) connection
failures.
In looking at the test, there is one place where it uses timeAllowed, and
then tries to make an assertion about the result -- either it will be
'complete', or if incomplete then it will meet some other garuntee...
// Regression check on timeAllowed in combination with sorting, SOLR-14758
// Should see either a complete result or a partial result, but never an NPE
rsp = queryAllowPartialResults("q", "text:d", "fl", "id", "sort", "payload
desc", "rows", "20", "timeAllowed", "1");
if (!Objects.equals(Boolean.TRUE,
rsp.getHeader().getBooleanArg(SolrQueryResponse.RESPONSE_HEADER_PARTIAL_RESULTS_KEY)))
{
assertFieldValues(rsp.getResults(), id, "11", "13", "12");
}
...but it never seems to fail with an assertion failure: it always seems
to fail with a "Connection refused" (maybe from an internal retry in
HttpSolrClient?)
my guess is that 2 things are colliding here:
1) for some/many seeds, this index only has one segment per shard, so
timeAllowed never matters ... but in oher seeds, the randomized
indexConfig causes a shard to have multiple segments, and the 1ms
timeAllowed (essentially) always trips.
2) at some point in the (recent) past, something changed in how
timeAllowed works in distributed searching (that may work fine in "real"
solr cloud, but maybe doesn't work as well in "fake"
BaseDistributedSearchTestCase type situations?) so that when the
timeAllowed condition is hit, the request doesn't fail the same way it use
to -- and the "client" (test code) is getting a RemoteSolrException
instead of the partial response it's expecting...
org.apache.solr.handler.component.DistributedQueryComponentCustomSortTest
> test FAILED
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException:
Error from server at http://127.0.0.1:33555/collection1:
org.apache.solr.client.solrj.SolrServerException: Connection refused
at
__randomizedtesting.SeedInfo.seed([5B595A296E3623CE:D30D65F3C0CA4E36]:0)
at
app//org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:668)
at
app//org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:239)
at
app//org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:222)
at
app//org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:226)
at
app//org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:1004)
at
app//org.apache.solr.client.solrj.SolrClient.query(SolrClient.java:1019)
at
app//org.apache.solr.BaseDistributedSearchTestCase.queryServer(BaseDistributedSearchTestCase.java:623)
: Date: Mon, 22 Nov 2021 07:30:25 -0500
: From: Eric Pugh <ep...@opensourceconnections.com>
: Reply-To: dev@solr.apache.org
: To: dev@solr.apache.org
: Subject: Can someone explain how -Ptest.seed works (Oh and
: DistributedQueryComponentCustomSortTest keeps failing!)?
:
: Can someone explain how the -Ptest.seed works, and how I use it to figure out
if a bug exists?
:
: I ran the full set of tests, and had this message:
: ERROR: The following test(s) have failed:
: -
org.apache.solr.handler.component.DistributedQueryComponentCustomSortTest.test
(:solr:core)
: Test output:
/Users/epugh/Documents/projects/solr-epugh-2/solr/core/build/test-results/test/outputs/OUTPUT-org.apache.solr.handler.component.DistributedQueryComponentCustomSortTest.txt
: Reproduce with: gradlew :solr:core:test --tests
"org.apache.solr.handler.component.DistributedQueryComponentCustomSortTest.test"
-Ptests.jvms=4 -Ptests.jvmargs=-XX:TieredStopAtLevel=1
-Ptests.seed=5B595A296E3623CE -Ptests.file.encoding=US-ASCII
:
:
: I then tried the same tests, but with out the -Ptests.seed, and it passed!
Does this mean there is a bug or not?
:
: I did go and check
:
:
http://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html#series/org.apache.solr.handler.component.DistributedQueryComponentCustomSortTest.test
:
: And it appears that this test has been failing more since July.
:
: Eric
:
:
:
: _______________________
: Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
http://www.opensourceconnections.com <http://www.opensourceconnections.com/> |
My Free/Busy <http://tinyurl.com/eric-cal>
: Co-Author: Apache Solr Enterprise Search Server, 3rd Ed
<https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
: This e-mail and all contents, including attachments, is considered to be
Company Confidential unless explicitly stated otherwise, regardless of whether
attachments are marked as such.
:
:
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org
