-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[PLAT-16832]: Set Flag ysql_yb_major_version_upgrade_compatibility on…
…ly when upgrade/rollback is in-progress Summary: As per this thread: https://yugabyte.slack.com/archives/C07DG9B7C3T/p1740011485617489 Earlier, YBA used to set the flag with value right from the start of the upgrade until the upgrade is rolled back or finalized. The flag also needs to be set even during the monitoring phase on all existing and new nodes. But now YBA is only supposed to set the flag when upgrade/rollback is in progress. So, YBA will set this flag at the start of upgrade/rollback and unset it at the end of upgrade/rollback. There is no need to configure this flag during the finalize upgrade process. Test Plan: Tested manually by performing an upgrade/rollback on both VM and K8s universes and verified from the logs and gflags server.conf file that flag was set while upgrade/rollback was in progress and unset after the task is completed. Verified that the flag is unset when the univ is in the monitoring phase, and any new node added in this phase also has the flag unset, unlike earlier. Reviewers: sanketh, anijhawan, sneelakantan Reviewed By: sanketh Subscribers: yugaware Differential Revision: https://phorge.dev.yugabyte.com/D42164
- Loading branch information
Showing
14 changed files
with
72 additions
and
158 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.