hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4406) read file failure,when the file is not close in secret mode
Date Wed, 16 Jan 2013 00:44:13 GMT

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

Aaron T. Myers commented on HDFS-4406:
--------------------------------------

Hi liaowenrui, can you comment about how to reproduce this issue, or perhaps attach a patch
with a test that reproduces this issue?

Also, can you comment about whether this issue actually caused you any problems other than
seeing this message in the logs? I believe the behavior of the DFSClient when it receives
this error is just to refetch a new BlockToken and then retry the request, so though you'll
see this error in the logs it should actually be innocuous.
                
> read file failure,when the file is not close in secret mode
> -----------------------------------------------------------
>
>                 Key: HDFS-4406
>                 URL: https://issues.apache.org/jira/browse/HDFS-4406
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0, 2.0.2-alpha
>            Reporter: liaowenrui
>            Priority: Critical
>         Attachments: BlockTokenSecretManager.patch
>
>
> 2013-01-14 18:27:06,216 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed
for 160.172.0.11:45176:null
> 2013-01-14 18:27:06,217 INFO org.apache.hadoop.ipc.Server: IPC Server listener on 50020:
readAndProcess threw exception javax.security.sasl.SaslException: DIGEST-MD5: IO error acquiring
password [Caused by org.apache.hadoop.security.token.SecretManager$InvalidToken: Can't re-compute
password for block_token_identifier (expiryDate=1358195226206, keyId=1639335405, userId=hbase,
blockPoolId=BP-myhacluster-25656, blockId=-6489888518203477527, access modes=[READ]), since
the required block key (keyID=1639335405) doesn't exist.] from client 160.172.0.11. Count
of bytes read: 0
> javax.security.sasl.SaslException: DIGEST-MD5: IO error acquiring password [Caused by
org.apache.hadoop.security.token.SecretManager$InvalidToken: Can't re-compute password for
block_token_identifier (expiryDate=1358195226206, keyId=1639335405, userId=hbase, blockPoolId=BP-myhacluster-25656,
blockId=-6489888518203477527, access modes=[READ]), since the required block key (keyID=1639335405)
doesn't exist.]
>         at com.sun.security.sasl.digest.DigestMD5Server.validateClientResponse(DigestMD5Server.java:577)
>         at com.sun.security.sasl.digest.DigestMD5Server.evaluateResponse(DigestMD5Server.java:226)
>         at org.apache.hadoop.ipc.Server$Connection.saslReadAndProcess(Server.java:1199)
>         at org.apache.hadoop.ipc.Server$Connection.readAndProcess(Server.java:1393)
>         at org.apache.hadoop.ipc.Server$Listener.doRead(Server.java:710)
>         at org.apache.hadoop.ipc.Server$Listener$Reader.doRunLoop(Server.java:509)
>         at org.apache.hadoop.ipc.Server$Listener$Reader.run(Server.java:484)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message