-
Notifications
You must be signed in to change notification settings - Fork 25k
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
IndexStatsIT#testFilterCacheStats fails #32506
Comments
Pinging @elastic/es-distributed |
I muted this test on the master and 6.x. |
I was able to reproduce this locally by simply running the test in a loop with |
@original-brownbear I did not look at this yet but I think it should be caused by a background merge. |
* Test randomly failed because of background merges * Fixed by force merging down to a single segment * Closes elastic#32506
* Test randomly failed because of background merges * Fixed by force merging down to a single segment * Closes #32506
* Test randomly failed because of background merges * Fixed by force merging down to a single segment * Closes #32506
seems like this happened again:
|
Link for the above https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+release-tests/221/ I'm not sure this is the same issue that lead to the initial problem. The failure now happens in a busy polling section of the test. I'll look into this. |
Added debug logging for this test in 75bfbe9, I couldn't even reproduce a single failing assertion inside the busy assert that fails now. Maybe we can learn more from the log. |
Haven't had this happen during the last 17 days it seems. It is conceivable that this was some freak timeout from super slow CI the logging suggests that the assertBusy loop that failed above has changes in the error on a second scale when that same loop locally takes |
There was another failure of this on January 4th, but the logs are missing |
Right ... one day after I posted the above ... adding the logs of that failure here for reference and will look into it (now we have debug logging active on this one at least). |
No recent failures -> closing |
This failed again on master: Does not reproduce locally for me with:
Stack trace:
Full build log: |
Just for future reference: the above is from https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=openjdk12,ES_RUNTIME_JAVA=java11,nodes=immutable&&linux&&docker/313/console I'll give this another look :) |
This again failed here: Did not reproduce locally:
Stack trace:
|
This failed again in 7.0 in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.0+matrix-java-periodic/ES_BUILD_JAVA=openjdk12,ES_RUNTIME_JAVA=zulu11,nodes=immutable&&linux&&docker/128/console The error is:
I got a failure the first time I tried to reproduce locally using:
The error I got was:
But it's not easily reproducible - I tried 5 more times and didn't see another failure. |
This has failed PR builds and fails frequently enough to warrant muting. |
* When close becomes true while the management pool is shut down, we run into an unhandled `EsRejectedExecutionException` that fails tests * Found this while trying to reproduce elastic#32506 * Running the IndexStatsIT in a loop is a way of reproducing this
* When close becomes true while the management pool is shut down, we run into an unhandled `EsRejectedExecutionException` that fails tests * Found this while trying to reproduce #32506 * Running the IndexStatsIT in a loop is a way of reproducing this
* When close becomes true while the management pool is shut down, we run into an unhandled `EsRejectedExecutionException` that fails tests * Found this while trying to reproduce elastic#32506 * Running the IndexStatsIT in a loop is a way of reproducing this
* When close becomes true while the management pool is shut down, we run into an unhandled `EsRejectedExecutionException` that fails tests * Found this while trying to reproduce #32506 * Running the IndexStatsIT in a loop is a way of reproducing this
If a background merge and refresh happens after a search but before a stats query, then evictions will be non-zero. Closes #32506
If a background merge and refresh happens after a search but before a stats query, then evictions will be non-zero. Closes #32506
If a background merge and refresh happens after a search but before a stats query, then evictions will be non-zero. Closes #32506
If a background merge and refresh happens after a search but before a stats query, then evictions will be non-zero. Closes #32506
If a background merge and refresh happens after a search but before a stats query, then evictions will be non-zero. Closes #32506
* When close becomes true while the management pool is shut down, we run into an unhandled `EsRejectedExecutionException` that fails tests * Found this while trying to reproduce elastic#32506 * Running the IndexStatsIT in a loop is a way of reproducing this
If a background merge and refresh happens after a search but before a stats query, then evictions will be non-zero. Closes elastic#32506
I think this failure relates to Lucene-7.5.
I can't reproduce this locally with this command:
CI: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java11,nodes=virtual&&linux/210/consoleText
Log: testFilterCacheStats.log
The text was updated successfully, but these errors were encountered: