Use NoOp engine for replicating closed indices #31745
Closed
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
This commit uses the NoOp engine introduced in elastic#31163 for closed indices. Instead of being removed from the routing table and essentially "dropped" (but not deleted), closed indices are now replicated the same way open indices are. Relates to elastic#31141
dakrone
added
review
:Distributed Indexing/Engine
|
Pinging @elastic/es-distributed |
This was referenced Jul 2, 2018
|
Closing this, as I believe we're going a different direction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 uses the NoOp engine introduced in #31163 for closed indices.
Instead of being removed from the routing table and essentially "dropped" (but
not deleted), closed indices are now replicated the same way open indices are.
Relates to #31141