On 21 July 2017 at 04:04, Erik Krogen wrote:
> Hi Kevin,
>
> Since you are using the "jhs" keytab with principal "jhs/_h...@realm.tld",
> the JHS is authenticating itself as the jhs user (which is the actual
> important part, rather than the user the process is running as).
I just realized that this problem is solved in version 2.9 and version
3.0 alpha 1 to 4. There you can set in yarn-site.xml the following
parameter yarn.nodemanager.default-container-executor.log-dirs.permissions.
I guess i will have to solve my problem with a bash script until the
version 2.9 is
Hi Kevin,
Since you are using the "jhs" keytab with principal "jhs/_h...@realm.tld",
the JHS is authenticating itself as the jhs user (which is the actual
important part, rather than the user the process is running as). If you
want it to be the "mapred" user, you should change the
Hi,
Thanks for the quick reply.
That was exactly the problem. The datanodes were throwing error of "maximum
IPC message length size not enough" but we were focusing on NameNodes only.
I changed the "ipc.maximum.data.length" property in core-site.xml file(I
found this solution of
Dn1 and Dn2 is re-started successfully..? can you check the DN logs..?
--Brahma Reddy Battula
From: omprakash [mailto:ompraka...@cdac.in]
Sent: 20 July 2017 12:12
To: user@hadoop.apache.org
Subject: Namenode not able to come out of SAFEMODE
Hi all,
I have a setup of 3 node Hadoop