roachtest/split: drop qps flavor of load-based split objective tests

Open Beginner friendly
#169,442 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
go

Research direction

Start in pkg/cmd/roachtest/tests/split.go at runLoadSplits and inspect the setLoadBasedRebalancingObjective helper. Remove the qps case while retaining CPU coverage, then check related expected split-count assertions. Done means the load-split objective tests remain valid with CPU-only coverage.

Written by the indexing model from the issue text.

Description

A-kv-distribution C-cleanup O-agent T-kv

Summary:
runLoadSplits (pkg/cmd/roachtest/tests/split.go:799) parameterizes its test cases over kv.allocator.load_based_rebalancing.objective, exercising both qps and cpu. This setting is read only by the legacy StoreRebalancer and has no effect under MMA.

MMA only ever balances on CPU, so the qps flavor of these tests is dead weight once MMA is the default (per #169430). Drop it; keep CPU coverage only.

Next Steps:

  • Remove the qps arm of the load-split objective matrix in split.go.
  • Drop or simplify the setLoadBasedRebalancingObjective helper if it loses its remaining caller.
  • Sanity-check that any related assertions (e.g. expected split counts) still hold under CPU-only.

Epic CRDB-56265

Jira issue: CRDB-63451

Dominant language
Go
Stars
32.5k
Forks
4.1k
Avg merge
2h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cockroachdb/cockroach

All issues in cockroachdb/cockroach

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.