-
Notifications
You must be signed in to change notification settings - Fork 589
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
CI Failure (Redpanda process unexpectedly stopped
) in MemoryStressTest.test_fetch_with_many_partitions
#11458
Comments
2 out of 3 brokers have OOMed with the same stack:
So effectively this is a case when #10905 does not prevent #3409 in all cases. I will be figuring out why exactly, but compared to v23.1 this is not a regression. |
Two more OOM cases: FAIL test: MemoryStressTest.test_fetch_with_many_partitions.memory_share_for_fetch=0.8 (3/31 runs) |
Closing this as it's a duplicate of #11304 |
Since the work has started here, doing the other way around - work for #11304 is done here |
FAIL test: MemoryStressTest.test_fetch_with_many_partitions.memory_share_for_fetch=0.8 (3/13 runs) |
https://buildkite.com/redpanda/redpanda/builds/31233#0188b78c-c490-4d04-8114-b49dcc1db720
The text was updated successfully, but these errors were encountered: