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.

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

Small improvements to resilience design docs #57791

Merged

Conversation

DaveCTurner
Copy link
Contributor

A follow-up to #47233 to clarify a few points.

A follow-up to elastic#47233 to clarify a few points.
@DaveCTurner DaveCTurner added >docs General docs changes :Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. v8.0.0 v7.8.1 v7.9.0 v7.7.2 labels Jun 8, 2020
@DaveCTurner DaveCTurner requested a review from jrodewig June 8, 2020 07:37
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (>docs)

@elasticmachine elasticmachine added the Team:Docs Meta label for docs team label Jun 8, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Cluster Coordination)

@elasticmachine elasticmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Jun 8, 2020
Copy link
Contributor Author

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

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

I looked at this again in situ with a fresh pair of eyes and found a few small suggestions.

* At least one copy of every <<scalability,shard>>.

We also recommend adding a new node to the cluster for each
Copy link
Contributor Author

Choose a reason for hiding this comment

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

More a requirement than a recommendation; added to the bullet-pointed list so it parallels the next one.

A resilient cluster requires redundancy for every required cluster component,
except the elected master node. For resilient clusters, we recommend:

* One elected master node
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is true, but it's not something the user needs to worry about. As long as you have at least three master-eligible nodes Elasticsearch will look after this point automatically.

automatically rebuilds any failed shard copies on the remaining nodes in order
to restore the cluster to full health after a failure.

Failures temporarily reduce the total capacity of your cluster. In addition,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We mention this in the "larger clusters" section but it applies to all clusters so I thought it'd help to note it here too.

the node fails, you may need to restore an older copy of any lost indices from a
<<modules-snapshots,snapshot>>. Because they are not resilient to any failures,
we do not recommend using one-node clusters in production.
store your data redundantly. However, by default at least one replica is
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added "by default" otherwise it's not true since you can have a green cluster with no replicas. My bad, I think this must have been an incomplete edit.

Copy link
Contributor

@jrodewig jrodewig left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks @DaveCTurner

@DaveCTurner DaveCTurner merged commit 6c92fac into elastic:master Jun 8, 2020
@DaveCTurner DaveCTurner deleted the 2020-06-08-resilience-docs-tweaks branch June 8, 2020 12:50
DaveCTurner added a commit that referenced this pull request Jun 8, 2020
A follow-up to #47233 to clarify a few points.
DaveCTurner added a commit that referenced this pull request Jun 8, 2020
A follow-up to #47233 to clarify a few points.
DaveCTurner added a commit that referenced this pull request Jun 8, 2020
A follow-up to #47233 to clarify a few points.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. >docs General docs changes Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. Team:Docs Meta label for docs team v7.7.2 v7.8.1 v7.9.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants