cockroach roachtest: increase expected ub sequential ranges 3 to 4

roachtest: increase expected ub sequential ranges 3 to 4

Open kvoli opened this issue 1 year ago • 1 comments

splits/load/sequential/nodes=3 would occasionally flake due to variable request timing between worker threads executing concurrent operations. For example, a later sequence 5 could be evaluated and recorded for load based splitting on the leaseholder prior to an earlier sequence 1. As a result, a load based split point may be returned for a key, because requests have fallen on both the left hand side and right hand side, despite the workload being sequential.

Bump the expected upper bound for ranges from 3 to 4.

Fixes: #118457 Fixes: #119442 Release note: None