cockroachdb / cockroachdb/cockroach

roachtest: ycsb/C/nodes=3 failed

Open
#175,687 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

branch-master C-test-failure O-roachtest O-robot release-blocker T-testeng
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

roachtest.ycsb/C/nodes=3 failed with artifacts on master @ 0ff013855fdee74d72243c42da24c01a62767848:

Failed with:

(cluster.go:3668).Run: full command output in run_091747.670371083_n4_cockroach-workload-r.log: COMMAND_PROBLEM: exit status 1
(monitor.go:329).Wait: monitor failure: monitor user task failed: t.Fatal() was called
test artifacts and logs in: /artifacts/ycsb/C/nodes=3/run_1

Cluster Node to Ip Mapping:

Node Public IP Private IP
teamcity-21524325-1789883542-109-n4cpu8-0001 172.210.8.64 10.1.0.143
teamcity-21524325-1789883542-109-n4cpu8-0002 20.42.106.199 10.1.0.111
teamcity-21524325-1789883542-109-n4cpu8-0003 20.102.44.154 10.1.0.142
teamcity-21524325-1789883542-109-n4cpu8-0004 20.106.179.140 10.1.0.145

Parameters:

  • arch=amd64
  • cloud=azure
  • coverageBuild=false
  • cpu=8
  • diskCount=0
  • encrypted=false
  • fs=ext4
  • localSSD=true
  • runtimeAssertionsBuild=false
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

See: Datadog Logs

/cc @cockroachlabs/test-eng

Improve this report!

Jira issue: CRDB-68573

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the roachtest README and the linked TeamCity artifacts for ycsb/C/nodes=3, especially run_091747.670371083_n4_cockroach-workload-r.log and /artifacts/ycsb/C/nodes=3/run_1. Use the linked Grafana and Datadog views to determine the failure cause; done means the underlying problem is fixed and this roachtest passes again.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.