cockroachdb / cockroachdb/cockroach
kv: two expiration based lease tests started failing
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
**Describe the problem**
This needs more investigation, but there are now two expiration based lease tests that are failing on master after April 30th.
[failover/non-system/deadlock/lease=expiration
](https://roachperf.crdb.dev/?filter=failover&view=failover%2Fnon-system%2Fdeadlock%2Flease%3Dexpiration&tab=gce)
and [failover/partial/lease-leader/lease=expiration](https://roachperf.crdb.dev/?filter=failover&view=failover%2Fpartial%2Flease-leader%2Flease%3Dexpiration&tab=gce)
This was likely due to 749cc5ad5673f80237b26ae2c85f5f39b6e43bf7, however in 7f1a55723f6d6b48eb9e3641ee234ddfce192334 we changed the setting for failover to "all ranges" but it still shows up as a problem.
**To Reproduce**
Run those two tests and notice that they don't recover.
Jira issue: CRDB-40299
Contributor guide
Assessment
This issue has not been assessed yet.