-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
fix(database): cgroup v2 compatibility #1963
Conversation
The memory check in the runOracle script takes the cgroup version into account. Fixes oracle#1939 Signed-off-by: Philippe Vanhaesendonck <philippe.vanhaesendonck@oracle.com>
I appreciate your input on this one.
If you think it is good to go, I'll push this fix for the other versions as well |
memory.max is what the container runtime uses and we can have memory.max < memory.high Signed-off-by: Philippe Vanhaesendonck <philippe.vanhaesendonck@oracle.com>
Looks good to me. |
Apply previous commit to the other DB container image scripts Signed-off-by: Philippe Vanhaesendonck <philippe.vanhaesendonck@oracle.com>
Applied the same changes to all scripts using Ready to be merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good for Single Instance files.
Needs @psaini79 to approve for the RAC case. |
Is there a chance to expedite this for Single Instance, i.e., file a PR with these changes for just the SI changes? :) |
I believe we gave @psaini79 sufficient time for review. I will merge it anyway. |
The memory check in the runOracle script takes the cgroup version into
account.
Fixes #1939
Signed-off-by: Philippe Vanhaesendonck philippe.vanhaesendonck@oracle.com