Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here. Want to know more about what has changed? Check out the Community News blog.

MapReduce job on Kerberized CDH 5.9.0 cluster causes YARN "User xxxxx not found"

Re: MapReduce job on Kerberized CDH 5.9.0 cluster causes YARN "User xxxxx not found"

Contributor

Hi,

 

I was under the impression that we didn't need "local" RHEL linux user on any nodes if we were using AD/LDAP ?

 

As you can see below, local user accounts don't exist:

 

[root@{obfuscated_client_edge_nodename}~]#   id dreeves
id: dreeves: no such user

 

 

But AD accounts do (you can also see there doesn't appear to be any AD-to-Linux GID/UID mappings either because I haven't worked out how to do this in AD):


[root@{obfuscated_client_edge_nodename}~]]#  id dreeves@{obfuscated_realm}


uid=33601114(dreeves@{obfuscated_domain}) gid=33600512 groups=33600512,33601105,33601106,33601107,33601109,33601111,33601112,33601113,33600513,33600572,33601197(datameer_users@{obfuscated_domain}),33601110(prod_hue_users@{obfuscated_domain}),33601108(prod_cm_users@{obfuscated_domain})

 

 

Thanks,

 

Damion.

 

Re: MapReduce job on Kerberized CDH 5.9.0 cluster causes YARN "User xxxxx not found"

Champion
It is a common misconception. Unless you config Hadoop to use LDAP to look up users it will use the default shell based lookup. So you still need local users or implement LDAP for RHEL. It looks like you have that pariltially in place. UID and gids are in place in AD. I don't know how you did it but you need to see how you can present the account without the domain name.

Re: MapReduce job on Kerberized CDH 5.9.0 cluster causes YARN "User xxxxx not found"

Explorer

check that user exists in all nodes with nodemanager rol.