Fix flaky ThreadPoolMergeSchedulerStressTestIT#139819
Merged
burqen merged 5 commits intoelastic:mainfrom Jan 8, 2026
Merged
Conversation
Increasing maxWaitTime for merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test stills fails on 10 minute timeout we can be quite sure that it hangs.
Some CI environments only have 4 cores and will fail this test if rnd gods are grumpy and generate a 5 or higher. NODE_PROCESSORS_SETTING is limited to the number of available processors.
burqen
added
the
:Distributed/Engine
elasticsearchmachine
added
Team:Distributed Indexing (obsolete)
Collaborator
|
Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing) |
Contributor
Author
|
The original test failures come from 9.1 so the fix need to be back ported. I will read up on how to do that. |
burqen
added
>test
elasticsearchmachine
added
v9.1.10
v9.2.4
v8.19.10
and removed
branch:9.2
branch:9.1
branch:8.19
labels
albertzaharovits
approved these changes
Jan 5, 2026
Contributor
albertzaharovits
left a comment
albertzaharovits
left a comment
There was a problem hiding this comment.
Thanks for looking into this!
…-137161-ThreadPoolMergeSchedulerStressTestIT
Contributor
Author
|
Failing due to other flaky test that is fixed here #140271 . Will hold of and wait for that one to be merged. |
…-137161-ThreadPoolMergeSchedulerStressTestIT
elasticsearchmachine
added
v8.19.11
v9.2.5
v9.1.11
and removed
v8.19.10
v9.2.4
v9.1.10
labels
This was referenced Jan 8, 2026
Collaborator
burqen
added a commit
to burqen/elasticsearch
that referenced
this pull request
Jan 8, 2026
* Increase wait time for flaky test Increasing maxWaitTime for merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test stills fails on 10 minute timeout we can be quite sure that it hangs. * Bind node processors setting in test Some CI environments only have 4 cores and will fail this test if rnd gods are grumpy and generate a 5 or higher. NODE_PROCESSORS_SETTING is limited to the number of available processors.
burqen
added a commit
to burqen/elasticsearch
that referenced
this pull request
Jan 8, 2026
* Increase wait time for flaky test Increasing maxWaitTime for merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test stills fails on 10 minute timeout we can be quite sure that it hangs. * Bind node processors setting in test Some CI environments only have 4 cores and will fail this test if rnd gods are grumpy and generate a 5 or higher. NODE_PROCESSORS_SETTING is limited to the number of available processors.
burqen
added a commit
to burqen/elasticsearch
that referenced
this pull request
Jan 8, 2026
* Increase wait time for flaky test Increasing maxWaitTime for merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test stills fails on 10 minute timeout we can be quite sure that it hangs. * Bind node processors setting in test Some CI environments only have 4 cores and will fail this test if rnd gods are grumpy and generate a 5 or higher. NODE_PROCESSORS_SETTING is limited to the number of available processors.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 8, 2026
* Increase wait time for flaky test Increasing maxWaitTime for merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test stills fails on 10 minute timeout we can be quite sure that it hangs. * Bind node processors setting in test Some CI environments only have 4 cores and will fail this test if rnd gods are grumpy and generate a 5 or higher. NODE_PROCESSORS_SETTING is limited to the number of available processors.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 8, 2026
* Increase wait time for flaky test Increasing maxWaitTime for merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test stills fails on 10 minute timeout we can be quite sure that it hangs. * Bind node processors setting in test Some CI environments only have 4 cores and will fail this test if rnd gods are grumpy and generate a 5 or higher. NODE_PROCESSORS_SETTING is limited to the number of available processors.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 9, 2026
* Increase wait time for flaky test Increasing maxWaitTime for merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test stills fails on 10 minute timeout we can be quite sure that it hangs. * Bind node processors setting in test Some CI environments only have 4 cores and will fail this test if rnd gods are grumpy and generate a 5 or higher. NODE_PROCESSORS_SETTING is limited to the number of available processors.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 9, 2026
* Increase wait time for flaky test Increasing maxWaitTime for merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test stills fails on 10 minute timeout we can be quite sure that it hangs. * Bind node processors setting in test Some CI environments only have 4 cores and will fail this test if rnd gods are grumpy and generate a 5 or higher. NODE_PROCESSORS_SETTING is limited to the number of available processors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Increase wait time for flaky test
Increasing
maxWaitTimefor merges to start and complete to 10 minutes. The previous time out of 1 minute leave room for scheduling variability to tip the test over the wait threshold and fail the test. If test still fails on 10 minute timeout we can be quite sure that it hangs.Bind max number generated for
node.processorssetting to available processors.Take care of issue #137161