-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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: uqo: OOM with st_collect #133337
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
Looks like we're processing some very large geometry values, leading to OOM. |
This comment was marked as off-topic.
This comment was marked as off-topic.
IIUC we first create very large geometry values via I'll extract the second failure on this issue into a separate one. |
136271: storage: cap prefix slice reuse between Flushes r=yuzefovich a=yuzefovich When using temporary storage, in `Put` we reuse the same byte slice by appending the new key to the unique prefix of the temporary storage. Previously, we would never reduce the capacity of the slice which could lead to us holding onto noticeable memory chunk (without accounting for it) if we happen to work with large keys. This commit improves the situation by ensuring that we don't keep the slice larger than 1MiB on every `Flush`. Informs: #133337. Epic: None Release note: None Co-authored-by: Yahor Yuzefovich <[email protected]>
Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.
roachtest.unoptimized-query-oracle/disable-rules=half/rand-tables failed with artifacts on master @ 9c1d89e3adb8c6532459cc3e616288db06f966d9:
Parameters:
ROACHTEST_arch=amd64
ROACHTEST_cloud=azure
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_runtimeAssertionsBuild=true
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
Grafana is not yet available for azure clusters
This test on roachdash | Improve this report!
Jira issue: CRDB-43547
The text was updated successfully, but these errors were encountered: