hadoop-hdfs-issues mailing list archives

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

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

Todd Lipcon commented on HDFS-4406:
-----------------------------------

Wouldn't the client get the InvalidAccessToken response, then go back to the new NameNode
to get the new block key? ie you might see this warning in the logs somewhere, but the client
should not actually fail to read the block.
                
> 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