Skip to content
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

Component operator is often OOMKill #1

Open
LHozzan opened this issue May 31, 2024 · 0 comments
Open

Component operator is often OOMKill #1

LHozzan opened this issue May 31, 2024 · 0 comments

Comments

@LHozzan
Copy link
Member

LHozzan commented May 31, 2024

  • situation occurring across our fleet
  • I dont see any anomalies from metrics, except memory usage
    OOMComponentManager
  • in previous run (marked yellow) component using more RAM
  • after OOMKill event (marked orange) RAM usage dropped
  • it seems, that in the memory space of the component are holding unrequired data, which can cause after some time of usage OOMKill event (I guess! I am not sure)
  • it is strange, that the component using same settings, managing same operators, but after OOMKill event is satisfied with lower memory usage
    OOMComponentManager_long

I would like to kindly ask to continue with the investigation in source code. Goal is, that operator will consume only constant and predictable amount of memory. If the state isnt possible to reach, I would like to ask you for explanation, why it isnt.

If you need more information, please, dont hesitate to ask and I will provide them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant