-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
[CCR] AutoFollowCoordinator and follower index already created #36540
Merged
martijnvg
merged 7 commits into
elastic:master
from
martijnvg:ccr_auto_follow_follower_index_already_exists
Dec 24, 2018
Merged
[CCR] AutoFollowCoordinator and follower index already created #36540
martijnvg
merged 7 commits into
elastic:master
from
martijnvg:ccr_auto_follow_follower_index_already_exists
Dec 24, 2018
Conversation
This file contains 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
The AutoFollowCoordinator should be resilient to the fact that the follower index has already been created and in that case it should only update the auto follow metadata with the fact that the follower index was created. Relates to elastic#33007
martijnvg
added
>enhancement
v7.0.0
:Distributed/CCR
Issues around the Cross Cluster State Replication features
v6.6.0
labels
Dec 12, 2018
Pinging @elastic/es-distributed |
10 tasks
…r_index_already_exists
…r_index_already_exists
@elasticmachine run the default distro tests |
…r_index_already_exists
jasontedor
approved these changes
Dec 23, 2018
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.
…r_index_already_exists
martijnvg
added a commit
that referenced
this pull request
Dec 24, 2018
The AutoFollowCoordinator should be resilient to the fact that the follower index has already been created and in that case it should only update the auto follow metadata with the fact that the follower index was created. Relates to #33007
martijnvg
added a commit
that referenced
this pull request
Dec 24, 2018
The AutoFollowCoordinator should be resilient to the fact that the follower index has already been created and in that case it should only update the auto follow metadata with the fact that the follower index was created. Relates to #33007
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Distributed/CCR
Issues around the Cross Cluster State Replication features
v6.6.0
v7.0.0-beta1
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.
The AutoFollowCoordinator should be resilient to the fact that the follower
index has already been created and in that case it should only update
the auto follow metadata with the fact that the follower index was created.
Relates to #33007