roachtest: set lower min range_max_bytes in multitenant_distsql test

[rharding6373]

The multitenant_distsql roachtest relies on a smaller range size than the new default min of range_max_bytes (64MiB) due to performance and resource limitations. We set the COCKROACH_MIN_RANGE_MAX_BYTES to allow the test to use the smaller range.

Fixes: #99626
Epic: None

Release note: None

[cockroach-teamcity]

This change is 

[mgartner]

@aliher1911 Does this seem sane to you? I think we need to do that same thing you did in #99636 to fix #99626.

[rharding6373]

Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @aliher1911, @renatolabs, and @srosenberg)

---

pkg/cmd/roachtest/tests/multitenant_distsql.go line 126 at r1 (raw file):

	// and test takes too long and too much resources with default range sizes
	// so make them much smaller.
	_, err = inst1Conn.Exec(`ALTER TABLE t CONFIGURE ZONE USING range_min_bytes = 1000,range_max_bytes = 100000`)

Just want to note that this is where we set the range_max_bytes in this test.

[aliher1911]

@mgartner It worked when run roachtests manually, but I'm yet to see it merge and pass nightly. If you want to be on a safe side, we can wait for my PR to merge and run overnight before merging. But I don't see why it could fail.

[rharding6373]

This passes the zone config checks when I test with roachtest manually, as well.

[mgartner]

I'd vote for merging this now. In the best case, we get less noise tomorrow. In the worst case, we have to find a new fix. At least we'll have more information.

[rharding6373]

TFTR!

bors r+

[craig]

Build failed (retrying...):

• Bazel Essential CI (Cockroach)

[craig]

Build failed (retrying...):

• Bazel Essential CI (Cockroach)

[craig]

Build failed (retrying...):

• Bazel Essential CI (Cockroach)

[rharding6373]

Will try again after flaky test fixes are in.

bors r-

[craig]

Canceled.

[rharding6373]

bors r+

[craig]

Build succeeded:

• Bazel Essential CI (Cockroach)

[renatolabs]

Sadly this doesn't seem to fix this set of roachtests. The statement to change range_max_bytes is issued against the tenant connection, and that tenant is still created without the env var, so it will still use the new range size defaults.

(The fact that we have separate code in multitenant_utils.go to start tenants replicating a lot of the logic of c.Start is also unfortunate, but I digress.)