-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CI] TransportSearchActionTests.testCollectSearchShards fails due to timeout #44563
Comments
Pinging @elastic/es-search |
Looking at build-stats, this one fails about 5 times a month, with either "failed to connect to remote clusters", or "expected latch to be counted down after 5s, but was not". Seems like the root cause could be the same for both errors. See this long comment for previous analysis on this one: #33852 (comment) . |
Pinging @elastic/es-distributed |
I don't see anything CCS or search specific in this failure, hence I relabeled it to :Distributed/Network. Let me know what I can do to help debug it. |
The first failure in newer history occurred on May 14th (previous one was January 23rd, which may speculatively have been caused by infra issues). This correlates somewhat with #40978 (April 8), which caused issues until #43983 (July 5). Notice that this test uses There is one newer 7.x build failure: https://scans.gradle.com/s/zpxr2bfpfnw2q, but this contains messages like this one:
and ran on debian, indicating it was hit by #43387. This is certainly not conclusive, but seems like a plausible explanation. Will leave this issue open for a while to see if we hit this error again. |
The test has not failed again, so will close this, assuming above explanation holds true. |
Intake build failed for branch 7.2:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.2+intake/262/console
Locally I could not reproduce this with following:
In the past, this has failed but was reported in another issue: #33852 (comment)
The text was updated successfully, but these errors were encountered: