Skip to content

Prevent non-data nodes to start with dangling indices #35447

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

Closed
wants to merge 6 commits into from

Conversation

vladimirdolzhenko
Copy link
Contributor

@vladimirdolzhenko vladimirdolzhenko commented Nov 12, 2018

Non data node (like pure master or pure coordinator node) could behaves like a data node in terms of picking up dangling indices for other data nodes will automatically import them.

This PR forbids non data nodes to start if any data shard folders in data path are found (presence of _state metadata folders are allowed for master node)

Closes #27073

@vladimirdolzhenko vladimirdolzhenko added the :Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can. label Nov 12, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Copy link
Contributor

@ywelsch ywelsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've left a few comments. Note that your check is never called on coordinating-only nodes.

@vladimirdolzhenko
Copy link
Contributor Author

@ywelsch I addressed your comments, could you pls have another look?

@vladimirdolzhenko
Copy link
Contributor Author

@elasticmachine run gradle build tests

@ywelsch
Copy link
Contributor

ywelsch commented Jan 25, 2019

superseded by #37347 and #37748

@ywelsch ywelsch closed this Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants