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

[Bug]: Kubernetes optimizer pod is frequently being killed #3451

Open
1 of 2 tasks
zhoujinsong opened this issue Mar 3, 2025 · 4 comments · May be fixed by #3458
Open
1 of 2 tasks

[Bug]: Kubernetes optimizer pod is frequently being killed #3451

zhoujinsong opened this issue Mar 3, 2025 · 4 comments · May be fixed by #3458
Assignees
Labels
type:bug Something isn't working
Milestone

Comments

@zhoujinsong
Copy link
Contributor

What happened?

Kubernetes optimizer's JVM heap memory limit is the same as the pod memory limit, which is the cause of the issue.

Affects Versions

master

What table formats are you seeing the problem on?

Iceberg

What engines are you seeing the problem on?

AMS, Optimizer

How to reproduce

  • Create a Kubernetes optimizer
  • Schedule some task to it

Relevant log output

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

  • I agree to follow this project's Code of Conduct
@zhoujinsong zhoujinsong added the type:bug Something isn't working label Mar 3, 2025
@Marvel-Gu
Copy link
Contributor

Please assign this to me. @zhoujinsong
I think it's necessary to allocate space for the JVM's non-heap memory so we need to set the JVM's heap memory smaller, right?

@XBaith
Copy link
Contributor

XBaith commented Mar 5, 2025

Thank you @Marvel-Gu. Assigned

@zhoujinsong
Copy link
Contributor Author

I think it's necessary to allocate space for the JVM's non-heap memory so we need to set the JVM's heap memory smaller, right?

Exactly. We should limit the size of the JVM heap memory, for example, to 80% of the pod's memory limit.

@XBaith
Copy link
Contributor

XBaith commented Mar 5, 2025

Exactly. We should limit the size of the JVM heap memory, for example, to 80% of the pod's memory limit.

+1. That is what I done

@zhoujinsong zhoujinsong added this to the Release 0.8.0 milestone Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants