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.

Sign up for GitHub

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

Jump to bottom

pool memory scenario acting strategy checking. #2

Closed

hurricane1026 opened this issue Feb 24, 2021 · 1 comment

Contributor

hurricane1026 commented Feb 24, 2021

if the OS's memory is in pool state, and sometimes the malloc/alloc return null or throw bad_alloc exception.

Arena should work correct. and give it some solutions, such as waiting? or return nullptr, or throw a exception?
Arena's client should have a solution to handle the Arena's failure.
STDB is high memory application, and because of seastar memory pools were isolated between CPU cores, so no memory can be alloced is a normal status.

Contributor Author

hurricane1026 commented Oct 16, 2023

move to linear

hurricane1026 closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment