-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Fix timeout in testDowngradeRemoteClusterToBasic #52284
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
Merged
Merged
Conversation
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
Pinging @elastic/es-distributed (:Distributed/CCR) |
ywelsch
approved these changes
Feb 13, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks Yannick. |
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this pull request
Feb 13, 2020
- ESCCRRestTestCase#ensureYellow does not work well with assertBusy - Increases timeout to 60s Closes elastic#52036
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this pull request
Feb 16, 2020
- ESCCRRestTestCase#ensureYellow does not work well with assertBusy - Increases timeout to 60s Closes elastic#52036 # Conflicts: # x-pack/plugin/ccr/qa/src/main/java/org/elasticsearch/xpack/ccr/ESCCRRestTestCase.java
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this pull request
Feb 17, 2020
…)" This reverts commit 30c98d6.
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this pull request
Feb 17, 2020
This commit restores the wait_for_no_initializing_shards check that was removed in elastic#52284. We need this condition when waiting for the yellow status on the follower because we bootstrap the primary shards of the follower using the snapshot/restore. Relates elastic#52284 Closes elastic#52126
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
>test
Issues or PRs that are addressing/adding tests
v6.8.7
v7.6.1
v7.7.0
v8.0.0-alpha1
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.
ESCCRRestTestCase#ensureYellow
does not work well withassertBusy
Closes #52036