cockroachdb / cockroachdb/cockroach

roachtest: replicagc-changed-peers/restart=false failed

Open
#175,681 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

roachtest.replicagc-changed-peers/restart=false failed with artifacts on master @ 0ff013855fdee74d72243c42da24c01a62767848:

Failed with:

(replicagc.go:337).waitForZeroReplicasOnN3: pq: could not determine data type of placeholder $1
test artifacts and logs in: /artifacts/replicagc-changed-peers/restart=false/run_1

Cluster Node to Ip Mapping:

Node Public IP Private IP
teamcity-21524325-1789883542-48-n6cpu4-0001 40.76.98.245 10.1.0.136
teamcity-21524325-1789883542-48-n6cpu4-0002 20.115.96.6 10.1.0.138
teamcity-21524325-1789883542-48-n6cpu4-0003 20.127.170.69 10.1.0.139
teamcity-21524325-1789883542-48-n6cpu4-0004 172.178.82.30 10.1.0.135
teamcity-21524325-1789883542-48-n6cpu4-0005 74.235.161.232 10.1.0.14
teamcity-21524325-1789883542-48-n6cpu4-0006 20.62.193.234 10.1.0.131

Parameters:

  • arch=amd64
  • cloud=azure
  • coverageBuild=false
  • cpu=4
  • diskCount=0
  • encrypted=false
  • metamorphicDRPC=true
  • metamorphicLeases=default
  • metamorphicWriteBuffering=true
  • runtimeAssertionsBuild=false
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

See: Datadog Logs

Same failure on other branches

  • #171810 release-26.3: roachtest: replicagc-changed-peers/restart=false failed [A-testing B-runtime-assertions-enabled C-bug C-test-failure O-roachtest O-robot P-3 T-kv branch-release-26.3]

/cc @cockroachlabs/kv-triage

Improve this report!

Jira issue: CRDB-68571

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 at replicagc.go:337, where waitForZeroReplicasOnN3 reports the placeholder-type error, then inspect the linked TeamCity logs and artifacts under /artifacts/replicagc-changed-peers/restart=false/run_1. Compare the related release-26.3 failure in #171810; done means the replicagc-changed-peers/restart=false roachtest completes without this SQL error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, distributed-systems, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.