[
https://issues.apache.org/jira/browse/HADOOP-19186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852512#comment-17852512
]
Srinivasu Majeti commented on HADOOP-19186:
-------------------------------------------
Hi [~arp] , I think we can print this log message only when debug enabled but
print it like WARN or ERROR instead of DEBUG so that we can easily catch it and
not missing like all other DEBUG msgs.
Current:
DEBUG org.apache.hadoop.security.UserGroupInformation: PrivilegedActionException
New
ERROR or WARN org.apache.hadoop.security.UserGroupInformation:
PrivilegedActionException
> Change loglevel to ERROR/WARNING so that it would easy to identify the
> problem without ignoring
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-19186
> URL: https://issues.apache.org/jira/browse/HADOOP-19186
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Reporter: Srinivasu Majeti
> Priority: Major
>
> On the new Host with Java version 11, the DN was not able to communicate with
> the NN. We enabled DEBUG logging for the DN and the below message was logged
> under DEBUG level.
> DEBUG org.apache.hadoop.security.UserGroupInformation:
> PrivilegedActionException
> as:hdfs/[email protected] (auth:KERBEROS)
> cause:javax.security.sasl.SaslExcept
> ion: GSS initiate failed [Caused by GSSException: No valid credentials
> provided (Mechanism level: Receive timed out)]
> Without a DEBUG level logging, this was shown up as a WARNING as below
> WARN org.apache.hadoop.ipc.Client: Couldn't setup connection for
> hdfs/[email protected] to
> avl2785p.bigdata.it.internal/172.24.178.32:8022
> javax.security.sasl.SaslException: GSS initiate failed [Caused by
> GSSException: No valid credentials provided (Mechanism level: Receive timed
> out)]
> A considerable amount of time was spent troubleshooting this issue as this
> exception was moved to a DEBUG level which was difficult to track in the logs.
> Can we have such critical WARNINGs shown up at the WARN/ERROR level so that
> it's not missed when we enable DEBUG level logging for datanodes?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
