cockroachdb / cockroachdb/cockroach

release-26.3.0-rc: roachtest: admission-control/multitenant-isolation/tpcc/noisy-neighbor failed

Open
#172,905 4 comments 0 reactions 0 assignees View on GitHub
A-admission-control A-testing branch-release-26.3.0-rc C-bug C-test-failure O-roachtest O-robot P-3 T-kv
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

roachtest.admission-control/multitenant-isolation/tpcc/noisy-neighbor [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/21444517?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/21444517?buildTab=artifacts#/admission-control/multitenant-isolation/tpcc/noisy-neighbor) on release-26.3.0-rc @ [0a3dc2524e335b85175c507a318dd57f28f92ef3](https://github.com/cockroachdb/cockroach/commits/0a3dc2524e335b85175c507a318dd57f28f92ef3):

Failed with:

```
(admission_control_multitenant_isolation.go:381).runMultiTenantIsolation: quiet tenant latency 21.976424ms exceeds max 20ms
test artifacts and logs in: /artifacts/admission-control/multitenant-isolation/tpcc/noisy-neighbor/run_1
```
Cluster Node to Ip Mapping:
| Node | Public IP | Private IP |
| --- | --- | --- |
| teamcity-21444517-1785303496-10-n3cpu4-0001 | 35.227.40.165 | 10.142.2.83 |
| teamcity-21444517-1785303496-10-n3cpu4-0002 | 136.108.11.245 | 10.142.2.105 |
| teamcity-21444517-1785303496-10-n3cpu4-0003 | 34.74.171.202 | 10.142.0.247 |

Parameters:
- arch=amd64
- cloud=gce
- coverageBuild=false
- cpu=4
- diskCount=0
- encrypted=false
- fs=ext4
- localSSD=false
- runtimeAssertionsBuild=false
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-21444517/admission-control-multitenant-isolation-tpcc-noisy-neighbor/1785303712383/1785305717272)

See: [Datadog Logs](https://us5.datadoghq.com/logs?query=service%3Aroachtest+%40cluster%3Ateamcity-21444517-1785303496-10-n3cpu4&from_ts=1785303712383&to_ts=1785305717272&live=false&storage=flex_tier)

/cc @cockroachlabs/admission-control

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*admission-control/multitenant-isolation/tpcc/noisy-neighbor.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-66188

Contributor guide

Open the contributing guide

Research direction

Start in admission_control_multitenant_isolation.go at line 381, then inspect the linked roachtest artifacts and logs for the noisy-neighbor run. Use the Grafana link to compare tenant latency during the failure; done means the cause is addressed and the test no longer exceeds its 20ms quiet-tenant limit.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.