W
[2021-09-17 18:13:19,547][INFO ][container.run ] Begin Elasticsearch startup script
[2021-09-17 18:13:19,555][INFO ][container.run ] Comparing the specified RAM to the maximum recommended for
Elasticsearch...
[2021-09-17 18:13:19,558][INFO ][container.run ] Inspecting the maximum RAM available...
[2021-09-17 18:13:19,561][ERROR][container.run ] 2021-09-17T18:13:19.562198180Z Unable to determine the maxi
mum allowable RAM for this host in order to configure Elasticsearch
Expected behavior
The pods should be able to run on cgroupv2.
Actual behavior
A clear and concise description of what actually happened.
To Reproduce
Steps to reproduce the behavior:
Enable cgroup V2 with MachineConfig on Openshift
Create a ClusterLogging Instance
The elasticsearch pods will stuck in crashLoopBackOff
Additional context
Hierarchy in cgroup v2 is different, and the path for memory limit is at /sys/fs/cgroup/memory.max
Describe the bug Elasticsearch pods can not start on systems with cgroup v2 enabled, probably due to this line: https://github.com/openshift/origin-aggregated-logging/blob/master/elasticsearch/run.sh#L56
Environment
Logs
Expected behavior The pods should be able to run on cgroupv2.
Actual behavior A clear and concise description of what actually happened.
To Reproduce Steps to reproduce the behavior:
Additional context Hierarchy in cgroup v2 is different, and the path for memory limit is at
/sys/fs/cgroup/memory.max