[ https://issues.apache.org/jira/browse/HDFS-14231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kitti Nanasi updated HDFS-14231: -------------------------------- Status: Patch Available (was: Open) > DataXceiver#run() should not log exceptions caused by InvalidToken exception > as an error > ---------------------------------------------------------------------------------------- > > Key: HDFS-14231 > URL: https://issues.apache.org/jira/browse/HDFS-14231 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs > Affects Versions: 3.1.1 > Reporter: Kitti Nanasi > Assignee: Kitti Nanasi > Priority: Major > Attachments: HDFS-14231.001.patch > > > HDFS-10760 changed the log level from error to trace in DataXceiver#run() if > the exception was an InvalidToken exception. I think it would be beneficial > to log on trace level if the exception's cause was InvalidException. Like in > the following case: > {code:java} > DataXceiver error processing unknown operation > src: xxx dst: xxx > javax.security.sasl.SaslException: DIGEST-MD5: IO error acquiring password > [Caused by org.apache.hadoop.security.token.SecretManager$InvalidToken: Block > token with block_token_identifier > (expiryDate=1547593336220, keyId=-1735471718, userId=hbase, > blockPoolId=BP-xxx, blockId=1245599303, access modes=[READ]) is expired.] > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org