Support Questions

Find answers, ask questions, and share your expertise

Cgroups Configuration on Cloudera

Explorer

Cloudera 6.2.0

Docker Centos 7 Image.

 

 

Hi All,

I am enabling the cgroups on all hosts of the Cloudera cluster. But after enabling cgroup roles are not starting on the hosts.

 

Error:

Error found before invoking supervisord: [Errno 2] No such file or directory: '/sys/fs/cgroup/cpuacct,cpu/system.slice/docker-542551d4e6b6ca6c6ab65a6f3b51c538b126a1762b36b35b7ba9023ed262f953.scope/185-yarn-RESOURCEMANAGER'

 

As I checked in host the below path exists:

/sys/fs/cgroup/cpuacct,cpu

but there is no "system.slice" folder exists inside /sys/fs/cgroup/cpuacct,cpu .

 

But there "system.slice" folder exists in /sys/fs/cgroup/cpuacct,cpu/systemd/system.slice/.

 

Can any one guide me how can I fix this error.?

 

Thanks.

 

 

3 REPLIES 3

Cloudera Employee

Hi All,

 

As per checking the error, The system expecting the path should be present under cgroups to write the Yarn resource manager but the path is not present. So please ask the OS team to create the path under the cgroup as below to get it fixed.

 

OS request to create a path /sys/fs/cgroup/cpuacct,cpu/system.slice

 

I could see that the above was already addressed in Cloudera Enterprise 5.11. So for a permanent solution, we recommend you to upgrade the version to 5.11.

 

Hope this clarifies your queries.

 

Regards,

Ela

Explorer
As I already mention I am using CDH 6.2.0 version. Also
I am not able to create a folder inside /sys/fs/cgroup/cpuacct,cpu/ as this is readonly file system.

Contributor
Hi @Nick

Error found before invoking supervisord: [Errno 2] No such file or directory: '/sys/fs/cgroup/cpuacct,cpu/system.slice/docker-542551d4e6b6ca6c6ab65a6f3b51c538b126a1762b36b35b7ba9023ed262f953.scope/185-yarn-RESOURCEMANAGER'

The above looks like you have this inside a Docker container. Please confirm.
- Could you do the following to help us understand this better

1. Have you tried running the docker as the privileged mode? if you do not have mounts configured?
#docker run -t -i --privileged os-flavor:os-version (example centos:6)

2. Create directory using root where the CM is trying to create the specified path:
#mkdir /sys/fs/cgroup/cpuacct,cpu/systemd/system.slice/

Let me know how it goes.

Thanks
V