Better handle OOM situations #106

New issue

Open

opened 2023-03-08 23:34:30 +00:00 by snegurochka · 0 comments

snegurochka commented

2023-03-08 23:34:30 +00:00

Member

Original issue: https://github.com/nspcc-dev/neofs-node/issues/2105

Sometimes our node can fail with OOM. It would be nice to have some pprof data in this scenarios.
Let's research possible ways to do this:

We can check if this is possible via external means and describe it in the documentation.
We can try to do this internally if pprof is enabled (may be introduce another setting). Related https://github.com/golang/go/issues/16843 . Here we can also adjust some runtime settings (pool sizes, gc timeouts, writecache background activity) in response to memory pressure.

Original issue: https://github.com/nspcc-dev/neofs-node/issues/2105 Sometimes our node can fail with OOM. It would be nice to have some pprof data in this scenarios. Let's research possible ways to do this: 1. We can check if this is possible via external means and describe it in the documentation. 2. We can try to do this internally if pprof is enabled (may be introduce another setting). Related https://github.com/golang/go/issues/16843 . Here we can also adjust some runtime settings (pool sizes, gc timeouts, writecache background activity) in response to memory pressure.