Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roachtest: multitenant/distsql/instances=20/bundle=off/timeout=1 failed #100260

Closed
cockroach-teamcity opened this issue Mar 31, 2023 · 14 comments · Fixed by #105006
Closed

roachtest: multitenant/distsql/instances=20/bundle=off/timeout=1 failed #100260

cockroach-teamcity opened this issue Mar 31, 2023 · 14 comments · Fixed by #105006
Assignees
Labels
A-kv Anything in KV that doesn't belong in a more specific category. branch-master Failures and bugs on the master branch. C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. skipped-test T-kv KV Team
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Mar 31, 2023

roachtest.multitenant/distsql/instances=20/bundle=off/timeout=1 failed with artifacts on master @ 41581c367b3a1d7893c2945465c57ffa841035e3:

test artifacts and logs in: /artifacts/multitenant/distsql/instances=20/bundle=off/timeout=1/run_1
(assertions.go:262).Fail: 
	Error Trace:	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:127
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:44
	            				main/pkg/cmd/roachtest/test_runner.go:995
	            				GOROOT/src/runtime/asm_amd64.s:1594
	Error:      	Received unexpected error:
	            	pq: could not validate zone config: RangeMaxBytes 100000 less than minimum allowed 67108864
	Test:       	multitenant/distsql/instances=20/bundle=off/timeout=1
(require.go:1264).NoError: FailNow called
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

/cc @cockroachdb/sql-queries

This test on roachdash | Improve this report!

Jira issue: CRDB-26328

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels Mar 31, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Mar 31, 2023
@blathers-crl blathers-crl bot added the T-sql-queries SQL Queries Team label Mar 31, 2023
@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant/distsql/instances=20/bundle=off/timeout=1 failed with artifacts on master @ 41581c367b3a1d7893c2945465c57ffa841035e3:

test artifacts and logs in: /artifacts/multitenant/distsql/instances=20/bundle=off/timeout=1/run_1
(assertions.go:262).Fail: 
	Error Trace:	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:127
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:44
	            				main/pkg/cmd/roachtest/test_runner.go:995
	            				GOROOT/src/runtime/asm_amd64.s:1594
	Error:      	Received unexpected error:
	            	pq: could not validate zone config: RangeMaxBytes 100000 less than minimum allowed 67108864
	Test:       	multitenant/distsql/instances=20/bundle=off/timeout=1
(require.go:1264).NoError: FailNow called
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@mgartner
Copy link
Collaborator

This looks to be the same as #99626. It appears that #99759 did not fix the issue.

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant/distsql/instances=20/bundle=off/timeout=1 failed with artifacts on master @ 99102ddf4b7602788b422366f1acc14b81c64d24:

test artifacts and logs in: /artifacts/multitenant/distsql/instances=20/bundle=off/timeout=1/run_1
(assertions.go:262).Fail: 
	Error Trace:	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:127
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:44
	            				main/pkg/cmd/roachtest/test_runner.go:995
	            				GOROOT/src/runtime/asm_amd64.s:1594
	Error:      	Received unexpected error:
	            	pq: could not validate zone config: RangeMaxBytes 100000 less than minimum allowed 67108864
	Test:       	multitenant/distsql/instances=20/bundle=off/timeout=1
(require.go:1264).NoError: FailNow called
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant/distsql/instances=20/bundle=off/timeout=1 failed with artifacts on master @ 99102ddf4b7602788b422366f1acc14b81c64d24:

test artifacts and logs in: /artifacts/multitenant/distsql/instances=20/bundle=off/timeout=1/run_1
(assertions.go:262).Fail: 
	Error Trace:	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:127
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:44
	            				main/pkg/cmd/roachtest/test_runner.go:995
	            				GOROOT/src/runtime/asm_amd64.s:1594
	Error:      	Received unexpected error:
	            	pq: could not validate zone config: RangeMaxBytes 100000 less than minimum allowed 67108864
	Test:       	multitenant/distsql/instances=20/bundle=off/timeout=1
(require.go:1264).NoError: FailNow called
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant/distsql/instances=20/bundle=off/timeout=1 failed with artifacts on master @ 1e27c65fb5a3810a5e2285cf07b45d95d401cca6:

test artifacts and logs in: /artifacts/multitenant/distsql/instances=20/bundle=off/timeout=1/run_1
(assertions.go:262).Fail: 
	Error Trace:	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:127
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:44
	            				main/pkg/cmd/roachtest/test_runner.go:995
	            				GOROOT/src/runtime/asm_amd64.s:1594
	Error:      	Received unexpected error:
	            	pq: could not validate zone config: RangeMaxBytes 100000 less than minimum allowed 67108864
	Test:       	multitenant/distsql/instances=20/bundle=off/timeout=1
(require.go:1264).NoError: FailNow called
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant/distsql/instances=20/bundle=off/timeout=1 failed with artifacts on master @ 1e27c65fb5a3810a5e2285cf07b45d95d401cca6:

test artifacts and logs in: /artifacts/multitenant/distsql/instances=20/bundle=off/timeout=1/run_1
(assertions.go:262).Fail: 
	Error Trace:	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:127
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:44
	            				main/pkg/cmd/roachtest/test_runner.go:995
	            				GOROOT/src/runtime/asm_amd64.s:1594
	Error:      	Received unexpected error:
	            	pq: could not validate zone config: RangeMaxBytes 100000 less than minimum allowed 67108864
	Test:       	multitenant/distsql/instances=20/bundle=off/timeout=1
(require.go:1264).NoError: FailNow called
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

roachtest.multitenant/distsql/instances=20/bundle=off/timeout=1 failed with artifacts on master @ 1e27c65fb5a3810a5e2285cf07b45d95d401cca6:

test artifacts and logs in: /artifacts/multitenant/distsql/instances=20/bundle=off/timeout=1/run_1
(assertions.go:262).Fail: 
	Error Trace:	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:127
	            				github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/multitenant_distsql.go:44
	            				main/pkg/cmd/roachtest/test_runner.go:995
	            				GOROOT/src/runtime/asm_amd64.s:1594
	Error:      	Received unexpected error:
	            	pq: could not validate zone config: RangeMaxBytes 100000 less than minimum allowed 67108864
	Test:       	multitenant/distsql/instances=20/bundle=off/timeout=1
(require.go:1264).NoError: FailNow called
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled
(cluster.go:1978).Run: cluster.RunE: context canceled

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

This test on roachdash | Improve this report!

@DrewKimball
Copy link
Collaborator

ALTER TABLE t CONFIGURE ZONE USING range_min_bytes = 1000, range_max_bytes = 100000

Could we set the min first, then do a succeedsSoon for the max?

@DrewKimball
Copy link
Collaborator

That command just fails even when run directly in the shell for an unloaded test cluster:

root@localhost:26257/defaultdb> ALTER TABLE country CONFIGURE ZONE USING range_min_bytes = 1000,range_max_bytes = 100000;
ERROR: could not validate zone config: RangeMaxBytes 100000 less than minimum allowed 67108864

...but it can't be done separately, either:

root@localhost:26257/defaultdb> ALTER TABLE country CONFIGURE ZONE USING range_min_bytes = 1000;
ERROR: could not validate zone config: range_min_bytes and range_max_bytes must be set together
SQLSTATE: 22023
HINT: try ALTER ... CONFIGURE ZONE USING <field_name> = COPY FROM PARENT [, ...] to populate the field

So I think we just have to figure out why #99759 didn't work.

@shralex shralex self-assigned this Apr 3, 2023
@mgartner mgartner removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Apr 3, 2023
@mgartner
Copy link
Collaborator

mgartner commented Apr 3, 2023

This is not a release-blocker.

craig bot pushed a commit that referenced this issue Apr 3, 2023
99858: screl: Add IndexID as a attr of UniqueWithoutIndex element r=Xiang-Gu a=Xiang-Gu

Previously, ALTER TABLE stmt where we add column/drop column/alter PK and adding a unique without index is problematic in that the it can succeed even when there are duplicate values. We already had a dep rule that enforces the new primary index to be backfilled before we validate the constraint against it. Unfortunately, this rule is not enforced on unique without index constraint because IndexID was not a attr of it. This commit fixes this.

Fixes #99281
Epic: None
Release note (bug fix): Fixed a bug in v23.1 in the declarative schema changer where unique without index can be incorrectly added in tables with duplicate values if it's with a ADD/DROP COLUMN in one ALTER TABLE statement.


100357: sql: allow changing the number of histogram samples and buckets r=rytaft a=rytaft

Informs #72418
Informs #97701

Release note (sql change): Added two new cluster settings that enable users to change the number of histogram samples and buckets collected when building histograms as part of table statistics collection: `sql.stats.histogram_samples.count` and `sql.stats.histogram_buckets.count`. While the default values should work for most cases, it may be beneficial to increase the number of samples and buckets for very large tables to avoid creating a histogram that misses important values.

100489: go.mod: bump Pebble to b84a7ec7d8dc r=RaduBerinde a=jbowens

```
b84a7ec7 db: populate return statistics for flushable ingests
5fd58365 objstorage: implement tracing
7f7451f2 db,record: add BatchCommitStats to measure total and component durations for commit
295aaab0 objstorage: implement basic refcounting
```

Epic: None
Release note: None

100516: multiregionccl: reenable TestMrSystemDatabase r=ajwerner a=ajwerner

I stressed this for a long time on many cores and it did not fail.

Epic: none

Fixes: #98039

Release note: None

100527: roachtest: skip multitenant/distsql for now r=yuzefovich a=yuzefovich

Informs: #100260.

Epic: None

Release note: None

Co-authored-by: Xiang Gu <[email protected]>
Co-authored-by: Rebecca Taft <[email protected]>
Co-authored-by: Jackson Owens <[email protected]>
Co-authored-by: Andrew Werner <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
@shralex shralex assigned arulajmani and unassigned shralex Apr 3, 2023
@renatolabs
Copy link
Contributor

So I think we just have to figure out why #99759 didn't work.

I left a comment on that PR; I think the env var needs to be passed to the command that starts the tenant.

#99759 (comment)

@blathers-crl blathers-crl bot added the T-kv KV Team label Apr 4, 2023
@pav-kv pav-kv added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-kv Anything in KV that doesn't belong in a more specific category. labels Apr 4, 2023
@exalate-issue-sync exalate-issue-sync bot removed the T-sql-queries SQL Queries Team label May 18, 2023
@nvanbenschoten
Copy link
Member

I see that the test is dropping the max range size in order to create a large number of splits. Does someone who is familiar with this test (maybe @cucaroach, its author) know why this approach was taken, as opposed to manually splitting ranges using ALTER TABLE _ SPLIT AT? My understanding is that this is supported by secondary tenants these days. Maybe it was not at the time?

@cucaroach
Copy link
Contributor

Setting the max range size was the only thing that occurred to me from what I can recall. I'm basically inserting rows and waiting for the number of ranges to grow high enough for distsql to hit all nodes and I wanted to get there as expediently as possible.

@herkolategan
Copy link
Collaborator

herkolategan commented Jun 15, 2023

@renatolabs your argument appears to be valid, I confirmed locally. By passing COCKROACH_MIN_RANGE_MAX_BYTES to start tenant as well it is working. I put out a PR [1] for the fix and we can cycle this test in again after that. Also made a small fix to the local testing part of it, since the ports were clashing.

I'll address the differences between roachprod & roachtest for multi-tenant operations in follow-up PRs related to overall multi-tenancy support in roachprod

[1] #105006

craig bot pushed a commit that referenced this issue Jun 19, 2023
105006: roachtest: multi-tenant distributed sql fix r=srosenberg,renatolabs a=herkolategan

This change fixes the `multitenant_distsql` test by passing `COCKROACH_MIN_RANGE_MAX_BYTES` as part of the env vars when starting tenants as well.

The code around port handling on local clusters have also been updated to avoid collisions. There is a mechanism in place to offset the ports, but it still clashed with local ports from other nodes created before the tenants, so a simple naive shift has been put in place.

Fixes: #100260
Epic: None

Co-authored-by: Herko Lategan <[email protected]>
@craig craig bot closed this as completed in ab9f165 Jun 19, 2023
herkolategan added a commit to herkolategan/cockroach that referenced this issue Jun 23, 2023
This change fixes the `multitenant_distsql` test by passing
`COCKROACH_MIN_RANGE_MAX_BYTES` as part of the env vars when starting tenants as
well.

The code around port handling on local clusters have also been updated to avoid
collisions. There is a mechanism in place to offset the ports, but it still
clashed with local ports from other nodes created before the tenants, so a
simple naive shift has been put in place.

Fixes: cockroachdb#100260
Epic: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-kv Anything in KV that doesn't belong in a more specific category. branch-master Failures and bugs on the master branch. C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. skipped-test T-kv KV Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.