-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: sysbench/oltp_update_index/nodes=3/cpu=32/conc=256 failed #97389
Comments
Node 3 panics with "use of Span after Finish":
The [1]
|
cc @cockroachdb/replication |
FYI, I believe this happened again in this failure. |
@aliher1911 Can you have a look at this when you get a chance? |
These are only fatal in test builds. Downgrading to GA blocker. |
The underlying failure here is "Was the raft log corrupted, truncated, or lost?" as in #97926. I'm checking why we have a problem with dist sender span because of this. |
In this case this is replica 2 on node 3 which is lagging behind
There are lots of log lines like
prior to node panic-ing. Mind they are for other logs, not the one that caused panic. This is tangental to why context/span was incorrectly closed when shutting down listeners. |
This is indeed a dupe of #97926, marking as such.
|
roachtest.sysbench/oltp_update_index/nodes=3/cpu=32/conc=256 failed with artifacts on master @ dd2749ae4ab61eed2f99238acb74e8d3c6b4cb1d:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=32
,ROACHTEST_encrypted=false
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-24671
The text was updated successfully, but these errors were encountered: