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.

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

Address jnpl-slave OOM'd Due to Mismatch Between cgroups and Java #44

Closed
damaestro opened this issue Aug 5, 2018 · 2 comments
Closed

Address jnpl-slave OOM'd Due to Mismatch Between cgroups and Java #44

damaestro opened this issue Aug 5, 2018 · 2 comments

Comments

@damaestro
Copy link
Contributor

It seems that using a node type other than n1-standard-1 causes the jenkins agent to get oom killed by k8s. This seems to be a mismatch between what java decides is it's heap and what the cluster is going to allow.

https://dzone.com/articles/why-my-java-application-is-oomkilled
@damaestro
Copy link
Contributor Author

https://bugzilla.redhat.com/show_bug.cgi?id=1515968

@damaestro
Copy link
Contributor Author

https://developers.redhat.com/blog/2017/04/04/openjdk-and-containers/

damaestro added a commit that referenced this issue Aug 21, 2018
@damaestro
Disable TLS until #44 (Java OOM) is addressed.
00d09bc
@damaestro damaestro mentioned this issue Aug 21, 2018
Merged
damaestro added a commit that referenced this issue Aug 21, 2018
@damaestro
Re-enable TLS now that #44 is resolved.
cf656fc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@damaestro