You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
roachtest: fix missing binary for TPC-C in multitenant upgrade test
Summary: In multitenant upgrade tests, the TPC-C workload may fail if the
required binary is missing on a node. This issue can occur when no tenant
is created on nodes with the previous binary version, and the workload
attempts to run using that binary.
A sample excerpt from the upgrade plan illustrates the process:
```
├── start cluster at version "v23.2.20" (1)
├── wait for all nodes (:1-4) to acknowledge cluster version '23.2' on system tenant (2)
├── set cluster setting "storage.ingest_split.enabled" to 'false' on system tenant (3)
├── run "maybe create some tenants" (4)
├── upgrade cluster from "v23.2.20" to "v24.1.13"
│ ├── prevent auto-upgrades on system tenant by setting `preserve_downgrade_option` (5)
│ ├── upgrade nodes :1-4 from "v23.2.20" to "v24.1.13"
│ │ ├── restart node 2 with binary version v24.1.13 (6)
│ │ ├── restart node 1 with binary version v24.1.13 (7)
│ │ ├── allow upgrade to happen on system tenant by resetting `preserve_downgrade_option` (8)
│ │ ├── restart node 3 with binary version v24.1.13 (9)
│ │ ├── restart node 4 with binary version v24.1.13 (10)
│ │ └── run "run workload on tenants" (11)
│ ├── run "run workload on tenants" (12)
```
Once all the nodes are upgraded (step 10), we enter the finalizing phase in
step 11. Our cluster configuration would then look like this,
```
[mixed-version-test/11_run-run-workload-on-tenants] 2025/03/13 10:47:21 runner.go:423: current cluster configuration:
n1 n2 n3 n4
released versions v24.1.13 v24.1.13 v24.1.13 v24.1.13
binary versions 24.1 24.1 24.1 24.1
cluster versions 24.1 24.1 24.1 24.1
```
This implies that our tenant would also start with the target version as we
finalize (see #138233). Then we run the TPC-C workload on tenant nodes
using the version we are migrating from—likely for compatibility reasons.
However, the required binary may be absent if, during step 4, we did not
create any tenants with the previous version due to probabilistic
selection. The fix is simple: upload the binary used to run TPC-C. The
process first checks whether the binary is already present, so no extra
performance overhead occurs if it is.
Fixes: #140507
Informs: #142807
Release note: None
Epic: None
0 commit comments