[
https://issues.apache.org/jira/browse/HDFS-5766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873372#comment-13873372
]
Hudson commented on HDFS-5766:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1671 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1671/])
HDFS-5766. In DFSInputStream, do not add datanode to deadNodes after
InvalidEncryptionKeyException in fetchBlockByteRange (Liang Xie via Colin
Patrick McCabe) (cmccabe:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1558536)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSInputStream.java
> In DFSInputStream, do not add datanode to deadNodes after
> InvalidEncryptionKeyException in fetchBlockByteRange
> --------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-5766
> URL: https://issues.apache.org/jira/browse/HDFS-5766
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 3.0.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Fix For: 2.4.0
>
> Attachments: HDFS-5766.txt
>
>
> Found this issue when i read fetchBlockByteRange code:
> If we hit InvalidEncryptionKeyException, current logic is:
> 1) reduce the retry count
> 2) clearDataEncryptionKey
> 3) addToDeadNodes
> 4) retry in another loop...
> If i am correct, we should treat InvalidEncryptionKeyException similar with
> InvalidBlockToken branch, bypassing addToDeadNodes(), since it's a client
> related, not caused by DN side:)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
