-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
130194: roachtest: separate-process deployments in mixedversion r=herkolategan,DarrylWong,srosenberg a=renatolabs This commit adds support `separate-process` deployments in `mixedversion` tests. It is a natural enhancement of previous work where we introduced `shared-process` deployments. When a test runs in a `separate-process` deployment mode, each upgrade will involve restarting the binaries for both the system tenant (also known as the storage cluster), as well as for the application (non-system) tenant. The storage cluster needs to finalize its upgrade before the application tenant starts upgrading. Mixed-version functions can be called while the system tenant is upgrading and/or while the application tenant is upgrading. For simplicity, only one separate-process tenant is created, and handles traffic generated by the test. In addition, a SQL server is started on every node where we run a storage cluster binary. In other words, the two processes are colocated (without any form of resource allocation) on the same nodes. For now, separate-process deployments are disabled on a number of tests where it's known to fail. We should, over time, investigate these failures and re-enable the new deployment mode on them. Epic: none Release note: None Co-authored-by: Renato Costa <[email protected]>
- Loading branch information
Showing
33 changed files
with
1,339 additions
and
609 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
Oops, something went wrong.