[ https://issues.apache.org/jira/browse/HADOOP-19186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852491#comment-17852491 ]
Arpit Agarwal commented on HADOOP-19186: ---------------------------------------- Hi [~smajeti], this is most likely being logged at DEBUG to avoid spamming the service logs. > 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/av3l704p.bigdata.it.internal@PRODUCTION.LOCAL (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/av3l704p.bigdata.it.internal@PRODUCTION.LOCAL 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: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org