tiflash: update tiflash upgrade document #2769
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
birdstorm
reviewed
Apr 15, 2020
Contributor
birdstorm
left a comment
birdstorm
left a comment
There was a problem hiding this comment.
do we need to.confirm that tiflash is down before we run update?
birdstorm
approved these changes
Apr 15, 2020
yikeke
reviewed
Apr 15, 2020
yikeke
changed the title
yikeke
reviewed
Apr 15, 2020
Contributor
|
cherry pick to release-4.0 in PR #2772 |
yikeke
pushed a commit
that referenced
this pull request
Apr 15, 2020
yikeke
added
priority/P1
ran-huang
added
translation/done
5 tasks
5 tasks
rleungx
pushed a commit
to rleungx/docs-cn
that referenced
this pull request
May 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted? (Required)
tiflash currently does not support
tiup cluster upgradeWhich TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?