-
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: kv95/enc=false/nodes=3/cpu=32/no-admission failed [context oom] #84801
Comments
OOM-killed. Wouldn't surprise me if many of the other roachtest failures were too.
|
Looks like most of this is due to @cockroachdb/sql-experience @cockroachdb/sql-queries Does any of this ring a bell? memprof.2022-07-21T08_37_12.773.56908028848.pprof.gz Rooted here: |
I looked at it but didn't come up with anything, cf69a32 looks possibly related. |
roachtest.kv95/enc=false/nodes=3/cpu=32/no-admission failed with artifacts on master @ 457d724622e4fa2e62d6f4e7926509dbc7d18511:
Parameters: |
@yuzefovich Mind having a look? |
@yuzefovich it's not clear to me that we're always calling |
Yeah, I don't think we always do - but is that required? Is this what Go compiler often complains about with "possible leak of a context"? I think we can just defer the cancellation and we should be good. |
Yeah, it will leak a goroutine if you don't call cancel. |
No goroutine is involved if you stick to only using stdlib contexts, but it will leak something. |
roachtest.kv95/enc=false/nodes=3/cpu=32/no-admission failed with artifacts on master @ 457d724622e4fa2e62d6f4e7926509dbc7d18511:
Parameters:
ROACHTEST_cloud=aws
,ROACHTEST_cpu=32
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-17874
The text was updated successfully, but these errors were encountered: