cockroachdb / cockroachdb/cockroach
roachtest: cdc/frontier-persistence-benchmark/interval=10m/tables=10000/ranges=1 failed
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
roachtest.cdc/frontier-persistence-benchmark/interval=10m/tables=10000/ranges=1 [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21515291?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_Roachtests_RoachtestNightlyGcePrivateBazel/21515291?buildTab=artifacts#/cdc/frontier-persistence-benchmark/interval=10m/tables=10000/ranges=1) on release-25.4.17-rc @ [a50a3839f84bf68d8a947f16ba2fa728f055ca4e](https://github.com/cockroachdb/cockroach/commits/a50a3839f84bf68d8a947f16ba2fa728f055ca4e):
```
(monitor.go:267).Wait: monitor failure: changefeed[default]: max latency was more than allowed: 2m0.021529533s vs 2m0s
test artifacts and logs in: /artifacts/cdc/frontier-persistence-benchmark/interval=10m/tables=10000/ranges=1/run_1
```
Parameters:
- arch=amd64
- cloud=gce
- coverageBuild=false
- cpu=16
- encrypted=false
- fs=ext4
- localSSD=true
- runtimeAssertionsBuild=false
- ssd=0
Help
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
See: [Grafana](https://go.crdb.dev/roachtest-grafana/teamcity-21515291/cdc-frontier-persistence-benchmark-interval-10m-tables-10000-ra/1789367449255/1789370450235)
/cc @cockroachlabs/cdc
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*cdc/frontier-persistence-benchmark/interval=10m/tables=10000/ranges=1.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)
Contributor guide
Research direction
Start with the failure at monitor.go:267 and read the roachtest README for investigation context. Inspect the artifacts and logs under /artifacts/cdc/frontier-persistence-benchmark/interval=10m/tables=10000/ranges=1/run_1, then use the linked Grafana view to determine why max latency exceeded 2m. Done means the cause is identified and the benchmark no longer fails for this condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100