Member since
09-23-2016
18
Posts
3
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
8843 | 03-21-2018 09:07 AM | |
3879 | 01-12-2017 02:55 AM |
07-18-2018
06:37 PM
Similar issue has been resolved 🙂
... View more
01-12-2017
02:55 AM
@rguruvannagari Thank for your point out. I had check that my yarn config that found it doesn't enable using cgroups, then I turn it on. Then the cli can login and execute map reduce jobs. There some resolve steps for other guys information: 1. umount /sys/fs/cgroup/cpu,cpuacct 2. mkdir /cgroup/cpu 3. Disable the property CPU Scheduling & CPU Isolation 4. Ensure the property yarn.nodemanager.container-executor.class=org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor
yarn.nodemanager.linux-container-executor.resources-handler.class=org.apache.hadoop.yarn.server.nodemanager.util.DefaultLCEResourcesHandler
yarn.nodemanager.linux-container-executor.cgroups.hierarchy=/yarn
yarn.nodemanager.linux-container-executor.cgroups.mount = true
yarn.nodemanager.linux-container-executor.cgroups.mount-path=/cgroup
yarn.nodemanager.linux-container-executor.group=hadoop 5. Add the yarn.nodemanager.linux-container-executor.nonsecure-mode.local-user property and set it to the desired user. 6. Configure the LinuxContainerExecutor to run jobs as the user submitting the job by adding property yarn.nodemanager.linux-container-executor.nonsecure-mode.limit-users and setting it to false 7. set min.user.id to a lower value in /etc/hadoop/conf/container-executor.cfg in all NodeManagers. 8. Rest Yarn service. References: https://hadoop.apache.org/docs/r2.7.2/hadoop-yarn/hadoop-yarn-site/NodeManagerCgroups.html https://www.ibm.com/support/knowledgecenter/SSPT3X_4.2.0/com.ibm.swg.im.infosphere.biginsights.admin.doc/doc/admin_yarn_cgroups.html
... View more
04-17-2019
03:23 PM
Hello, Restarting the Standby NameNode did not resolve the issue. Then when trying to restart the Active NameNode Ambari told me to SSH into my Active NameNode server and: Enter Safe Mode sudo su hdfs -l -c 'hdfs dfsadmin -safemode enter' Safe mode is ON in xx.xxx.xxx.xxx:8020 Safe mode is ON in xx.xxx.xxx.xxx:8020 The save Namespace root@xxxxx:~# sudo su hdfs -l -c 'hdfs dfsadmin -saveNamespace' Save namespace successful for xx.xxx.xxx.xxx:8020 Save namespace successful for xx.xxx.xxx.xxx:8020 After that restarting both NameNodes cleared the Alerts. Regards.
... View more