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

Clarify rolling upgrade fallback to restart upgrade #42161

Conversation

Projects
None yet
4 participants
@DaveCTurner
Copy link
Contributor

commented May 15, 2019

Adds a note that restarting half-or-more of the master-eligible nodes means
you're no longer doing a rolling upgrade, and may need to upgrade all the
things before the cluster returns to health.

Clarify rolling upgrade fallback to restart upgrade
Adds a note that restarting half-or-more of the master-eligible nodes means
you're no longer doing a rolling upgrade, and may need to upgrade all the
things before the cluster returns to health.
@elasticmachine

This comment has been minimized.

Copy link

commented May 15, 2019

@ywelsch
Copy link
Contributor

left a comment

LGTM

@bleskes
Copy link
Member

left a comment

LGTM

@DaveCTurner DaveCTurner merged commit f3dbfdb into elastic:master May 16, 2019

4 checks passed

CLA All commits in pull request signed
Details
elasticsearch-ci/docbldesx Build finished.
Details
elasticsearch-ci/docs-check Build finished.
Details
elasticsearch-ci/oss-distro-docs Build finished.
Details

@DaveCTurner DaveCTurner deleted the DaveCTurner:2019-05-15-rolling-upgrade-docs-full-cluster-restart-fallback branch May 16, 2019

DaveCTurner added a commit that referenced this pull request May 16, 2019

Clarify rolling upgrade fallback to restart upgrade (#42161)
Adds a note that restarting half-or-more of the master-eligible nodes means
you're no longer doing a rolling upgrade, and may need to upgrade all the
things before the cluster returns to health.

DaveCTurner added a commit that referenced this pull request May 16, 2019

Clarify rolling upgrade fallback to restart upgrade (#42161)
Adds a note that restarting half-or-more of the master-eligible nodes means
you're no longer doing a rolling upgrade, and may need to upgrade all the
things before the cluster returns to health.

DaveCTurner added a commit that referenced this pull request May 16, 2019

Clarify rolling upgrade fallback to restart upgrade (#42161)
Adds a note that restarting half-or-more of the master-eligible nodes means
you're no longer doing a rolling upgrade, and may need to upgrade all the
things before the cluster returns to health.

Megamiun added a commit to Megamiun/elasticsearch that referenced this pull request May 18, 2019

Clarify rolling upgrade fallback to restart upgrade (elastic#42161)
Adds a note that restarting half-or-more of the master-eligible nodes means
you're no longer doing a rolling upgrade, and may need to upgrade all the
things before the cluster returns to health.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.