Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Provide smart approach to determine redundancy policy with self provisioned ES #502

Closed
objectiser opened this issue Jul 4, 2019 · 2 comments
Closed

Provide smart approach to determine redundancy policy with self provisioned ES #502

objectiser opened this issue Jul 4, 2019 · 2 comments
Labels
Elasticsearch The issues related to Elasticsearch storage

Comments

@objectiser
Copy link
Contributor

As discussed in #501, it would be good to provide a smart way to determine a default redundancy policy. Currently will default to ZeroRedundancy.
@jpkrohling jpkrohling added the Elasticsearch The issues related to Elasticsearch storage label Jul 16, 2019
@pavolloffay
Copy link
Member

See #501 (comment).

The redundancy policy cannot be determined just from the node count. The node count and redundancy policy are used to calculate replica shards.

I have submitted #531 to use single redundancy by default. I don't know any way we could optimize the current approach, it seems this could be closed if nobody knows a better way to handle this.

@objectiser
Copy link
Contributor Author

Agree, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Elasticsearch The issues related to Elasticsearch storage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jpkrohling @objectiser @pavolloffay