Hi John,
FWIW, setting the log level of org.apache.hadoop.security.UserGroupInformation
to ERROR seemed to prevent the fatal NameNode slowdown we ran into. Although I
still saw no such user Shell$ExitCodeException messages in the logs, these
only occurred every few minutes or so. Thus, it
Hi John,
My AWS Elastic MapReduce NameNode is also filling its log file with messages
like the following:
2014-02-18 23:56:52,344 WARN org.apache.hadoop.security.UserGroupInformation
(IPC Server handler 78 on 9000): No groups available for user
job_201402182309_0073
2014-02-18 23:56:52,351
It just seems like lazy code. You can see that, later, there is this:
{code}
for(Token? token : UserGroupInformation.getCurrentUser().getTokens())
{
childUGI.addToken(token);
}
{code}
So eventually the JobToken is getting added to the UGI which runs task-code.
Thanks Vinod for your quick response. It is running in non-secure mode.
I still don't get what is the purpose to use job id in UGI. Could you
please explain a bit more?
Thanks,
John
On Wed, Jan 8, 2014 at 10:11 AM, Vinod Kumar Vavilapalli
vino...@hortonworks.com wrote:
It just seems like
Looked a bit deeper and seems this code was introduced by the following
JIRA.
https://issues.apache.org/jira/browse/MAPREDUCE-1457
There is another related JIRA, i.e.,
https://issues.apache.org/jira/browse/MAPREDUCE-4329.
Perhaps, the warning message is a side effect of JIRA MAPREDUCE-1457 when
Hi,
I looked at Hadoop 1.X source code and found some logic that I could not
understand.
In the org.apache.hadoop.mapred.Child class, there were two UGIs defined as
follows.
UserGroupInformation current = UserGroupInformation.getCurrentUser();
current.addToken(jt);
