[ 
https://issues.apache.org/jira/browse/HDFS-14231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760310#comment-16760310
 ] 

Wei-Chiu Chuang commented on HDFS-14231:
----------------------------------------

+1

For posterity, this is usually seen on a secure HBase cluster, when HBase 
RegionServer opens a block for a long time and then reads the block after 10 
hours (block token expires after 10 hours by default). So nothing to panic 
about.

Additionally, the block token expiration message is logged prior to this 
message, like the following:
{noformat}

2019-01-16 03:32:23,809 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: 
Block token verification failed: op=REQUEST_SHORT_CIRCUIT_FDS, 
remoteAddress=unix:/var/run/hdfs-sockets/dn, message=Block token with 
block_token_identifi
er (expiryDate=1547569931036, keyId=xxxx, userId=hbase, blockPoolId=xxxx, 
blockId=xxxx, access modes=[READ]) is expired.{noformat}
So no need to log it again, especially not at ERROR level.

This is similar to HDFS-10760. The difference is that in this case, DataXceiver 
thread just got created, and the exception is thrown from a different code path.

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to