Skip to content

[ISSUE #36] Change default memory resource limit config to avoid broker pod OOMKilled error #41

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
Merged
liuruiyiyang merged 1 commit into from
Aug 25, 2020
Merged

[ISSUE #36] Change default memory resource limit config to avoid broker pod OOMKilled error #41

liuruiyiyang merged 1 commit into from
Aug 25, 2020

Conversation

@liuruiyiyang
Copy link
Contributor

@liuruiyiyang liuruiyiyang commented Aug 24, 2020 •
edited
Loading

Change List:

  1. Change default broker CRD resource limit memory size to 12GB to avoid issue broker OOMKilled #36
  2. Add related notice in README.

@liuruiyiyang liuruiyiyang changed the title Change default memory resource limit config to avoid broker pod OOMKilled error [ISSUE #36] Change default memory resource limit config to avoid broker pod OOMKilled error Aug 24, 2020
@liuruiyiyang liuruiyiyang merged commit db32f3f into master Aug 25, 2020
zhihui921016 pushed a commit to zhihui921016/rocketmq-operator that referenced this pull request Aug 28, 2020
@liuruiyiyang @zhihui921016
docs(README): change default memory resource limit config to avoid br…
13eeee2 
…oker pod OOMKilled error (apache#41)

Co-authored-by: liuruiyiyang <liurui@apache.org>
@liuruiyiyang liuruiyiyang deleted the change-default-resource-limit branch August 28, 2020 05:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@RongtongJin RongtongJin RongtongJin approved these changes

@duhenglucky duhenglucky Awaiting requested review from duhenglucky

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@liuruiyiyang @RongtongJin