forked from cockroachdb/cockroach
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
multitenant: randomly run tests with tenants
Previously, testServer would run by default in single-tenant mode. This PR changes testServer to run by default in multi-tenant mode, and runs all statements through the default test tenant. Since we want the bulk of our testing to remain in single-tenant mode, we only probabilistically run with tenants (with probability 0.25). This commit also contains a few pieces of cleanup which were necessary to make the testing changes (and were difficult to split into a separate commit): - Change the "Existing" flag on tenant start to "DisableCreateTenant" and make the tenant start code more tolerant of existing tenants by checking to see if the tenant exists before trying to create it. The DisableCreateTenant flag is required for the cases where we want a test to fail due to the lack of a created tenant. - Changed the multi-region backup tests to use node 0 instead of node 1, to allow them to work within a tenant. Tenants aren't able to access remote nodes of nodelocal stoarge. - Cleaned up a couple of cases where our error handling was passing nil structs to be printed out. - Had to special case the setting of kv.range_merge.queue_enabled because it is only available to the system SQL server. As a result, all tests which check for its setting had to be modified to no longer check for it (since it will only be set in the case where we have no SQL server). Additionally, we've created a tracking issue for all tests which currently don't work under the default test tenant (cockroachdb#76378). Release note: None
- Loading branch information
Showing
74 changed files
with
775 additions
and
174 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
Oops, something went wrong.