BTS-2246 | Known issue: --cluster.upgrade should not be set on DB-Servers
#827
+2
−0
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
Contributor
|
Deploy Preview Available Via |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Upstream PRs
Note
Add an upgrading-related known issue to 3.12 docs noting DB-Server failures when
--cluster.upgrade=onlineis used with--database.auto-upgrade=truein v3.12.6, fixed in v3.12.6-1.site/content/3.12/release-notes/version-3.12/known-issues-in-3-12.mdandsite/content/3.13/release-notes/version-3.12/known-issues-in-3-12.md.v3.12.6fails when--cluster.upgrade=onlineis combined with--database.auto-upgrade=true; option ignored on DB-Servers startingv3.12.6-1(BTS-2246).Written by Cursor Bugbot for commit 3a4fc3f. This will update automatically on new commits. Configure here.