[TEST] Removes timeout based wait_for_active_shards REST test #23360
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.
This commit removes a broken test that attempts to ensure, when
there are not enough nodes to allocate the
wait_for_active_shardsnumber of shards, that shardsAcknowledged returns false. We already
test for this in WaitForActiveShardsIT, and this test introduces a timeout
so we do not wait the full 30s before timing out and returning
shardsAcknowledged=false. A very small timeout, however, can cause the test
to fail for other reasons, namely that the master has not even gotten the chance
to update the cluster state with the newly created index. Increasing the timeout
here to allow index creation in the cluster state to complete adds more duration
to a test that is not really necessary. Hence, this test is being removed.