Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roachtest: tpccbench/nodes=3/cpu=16 failed #134639

Closed
cockroach-teamcity opened this issue Nov 8, 2024 · 3 comments
Closed

roachtest: tpccbench/nodes=3/cpu=16 failed #134639

cockroach-teamcity opened this issue Nov 8, 2024 · 3 comments
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-kv KV Team X-infra-flake the automatically generated issue was closed due to an infrastructure problem not a product issue

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Nov 8, 2024

roachtest.tpccbench/nodes=3/cpu=16 failed with artifacts on master @ a44a9b1ffce25f51026b494a1dcb393cfc5361f3:

(monitor.go:149).Wait: monitor failure: full command output in run_111030.156103855_n1_cockroach-workload-f.log: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/tpccbench/nodes=3/cpu=16/cpu_arch=arm64/run_1

Parameters:

  • ROACHTEST_arch=arm64
  • ROACHTEST_cloud=azure
  • ROACHTEST_coverageBuild=false
  • ROACHTEST_cpu=16
  • ROACHTEST_encrypted=false
  • ROACHTEST_fs=ext4
  • ROACHTEST_localSSD=true
  • ROACHTEST_runtimeAssertionsBuild=false
  • ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

Grafana is not yet available for azure clusters

/cc @cockroachdb/test-eng

This test on roachdash | Improve this report!

Jira issue: CRDB-44184

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-testeng TestEng Team labels Nov 8, 2024
@DarrylWong
Copy link
Contributor

Import failed with:

W241108 11:15:12.123814 1 ccl/workloadccl/fixture.go:577  [-] 6  error enabling automatic stats: pq: update-setting: result is ambiguous: error=ba: Put [/Table/6/1/"sql.stats.automatic_collection.enabled"/0], EndTxn(parallel commit) [/Table/6/1/"sql.stats.automatic_collection.enabled"/0], [txn: f973c1c1], [protect-ambiguous-replay] RPC error: grpc: error reading from server: EOF [code 14/Unavailable] [exhausted] (last error: failed to send RPC: sending to all replicas failed; last error: ba: Put [/Table/6/1/"sql.stats.automatic_collection.enabled"/0], EndTxn(parallel commit) [/Table/6/1/"sql.stats.automatic_collection.enabled"/0], [txn: f973c1c1], [protect-ambiguous-replay] RPC error: grpc: error reading from server: EOF [code 14/Unavailable])
Error: importing fixture: importing table customer: pq: pausing due to error; use RESUME JOB to try to proceed once the issue is resolved, or CANCEL JOB to rollback: exhausted retries: grpc: error reading from server: EOF [code 14/Unavailable]
run_111030.156103855_n1_cockroach-workload-f: 2024/11/08 11:15:12 cluster.go:2489: > result: COMMAND_PROBLEM: exit status 1

Node 1 was having trouble staying connected, logs are full of:

W241108 11:15:39.376260 599 kv/kvserver/liveness/liveness.go:667 â‹® [T1,Vsystem,n1,liveness-hb] 1573 +An inability to maintain liveness will prevent a node from participating in a
W241108 11:15:39.376260 599 kv/kvserver/liveness/liveness.go:667 â‹® [T1,Vsystem,n1,liveness-hb] 1573 +cluster. If this problem persists, it may be a sign of resource starvation or
W241108 11:15:39.376260 599 kv/kvserver/liveness/liveness.go:667 â‹® [T1,Vsystem,n1,liveness-hb] 1573 +of network connectivity problems. For help troubleshooting, visit:

Maybe just an infra flake but I'll send over to kv to take a closer look.

@DarrylWong DarrylWong added T-kv KV Team and removed T-testeng TestEng Team labels Nov 8, 2024
@srosenberg
Copy link
Member

It does look like network just dropped out on n1.

ip node
10.1.0.10 n1
10.1.0.101 n2
10.1.0.100 n3

From n2,

E241108 11:12:09.957964 861 2@rpc/peer.go:642 ⋮ [T1,Vsystem,n2,rnode=1,raddr=‹10.1.0.10:26257›,class=raft,rpc] 269  disconnected (was healthy for 1.001s): grpc: ‹rpc error: code = Unavailable desc = error reading from server: EOF› [code 14/Unavailable]
W241108 11:12:09.957968 15966 kv/kvserver/raft_transport.go:1067 ⋮ [T1,Vsystem,n2] 270  while processing outgoing Raft queue to node 1: recv msg error: grpc: ‹grpc: the client connection is closing› [code 1/Canceled]:
W241108 11:12:12.638239 955 kv/kvserver/raft_transport.go:1067 ⋮ [T1,Vsystem,n2] 271  while processing outgoing Raft queue to node 1: recv msg error: grpc: ‹error reading from server: read tcp 10.1.0.101:37850->10.1.0.10:26257: read: connection reset by peer› [code 14/Unavailable]:

From n1,

W241108 11:12:08.684625 23933 kv/kvserver/closedts/sidetransport/receiver.go:135 ⋮ [n1,remote=2] 409  closed timestamps side-transport connection dropped from node: 2 (grpc: ‹context canceled› [code 1/Canceled])
W241108 11:12:08.875542 254 2@gossip/gossip.go:1467 â‹® [T1,Vsystem,n1] 410  first range unavailable; trying remaining addresses
I241108 11:12:08.875683 24091 gossip/client.go:112 ⋮ [T1,Vsystem,n1] 411  unvalidated bootstrap gossip dial to ‹10.1.0.100:26257›
I241108 11:12:08.887057 24091 gossip/client.go:136 ⋮ [T1,Vsystem,n1] 412  started gossip client to n0 (‹10.1.0.100:26257›)
I241108 11:12:08.934968 24197 rpc/heartbeat.go:169 â‹® [-] 413  failing ping request from node n2
E241108 11:12:09.067784 2706 2@rpc/peer.go:642 ⋮ [T1,Vsystem,n1,rnode=2,raddr=‹10.1.0.101:26257›,class=raft,rpc] 414  disconnected (was healthy for 2m0.694s): grpc: ‹error reading from server: EOF› [code 14/Unavailable]

@srosenberg
Copy link
Member

Also, we're hitting AmbiguousReplayProtection [1].

[1] #107658

@tbg tbg closed this as completed Nov 11, 2024
@tbg tbg added X-infra-flake the automatically generated issue was closed due to an infrastructure problem not a product issue and removed release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. labels Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-kv KV Team X-infra-flake the automatically generated issue was closed due to an infrastructure problem not a product issue
Projects
None yet
Development

No branches or pull requests

4 participants