Skip to content

Use NoOp engine for replicating closed indices#31745

Closed
dakrone wants to merge 1 commit intoelastic:closed-index-replicationfrom
dakrone:use-noop-for-closed
Closed

Use NoOp engine for replicating closed indices#31745
dakrone wants to merge 1 commit intoelastic:closed-index-replicationfrom
dakrone:use-noop-for-closed

Conversation

@dakrone
Copy link
Copy Markdown
Member

@dakrone dakrone commented Jul 2, 2018

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

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 dakrone added review :Distributed/Engine Anything around managing Lucene and the Translog in an open shard. labels Jul 2, 2018
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-distributed

@dakrone
Copy link
Copy Markdown
Member Author

dakrone commented Jul 3, 2018

Closing this, as I believe we're going a different direction.

@dakrone dakrone closed this Jul 3, 2018
@dakrone dakrone deleted the use-noop-for-closed branch February 4, 2019 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed/Engine Anything around managing Lucene and the Translog in an open shard.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants