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

Hudson commented on HDFS-6362:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #5606 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/5606/])
HDFS-6362. InvalidateBlocks is inconsistent in usage of DatanodeUuid and 
StorageID. (Arpit Agarwal) (arp: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1595056)
* /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/server/blockmanagement/BlockManager.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/InvalidateBlocks.java


> InvalidateBlocks is inconsistent in usage of DatanodeUuid and StorageID
> -----------------------------------------------------------------------
>
>                 Key: HDFS-6362
>                 URL: https://issues.apache.org/jira/browse/HDFS-6362
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.4.0
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>            Priority: Blocker
>             Fix For: 3.0.0, 2.4.1
>
>         Attachments: HDFS-6362.01.patch, HDFS-6362.02.patch, 
> HDFS-6362.03.patch, HDFS-6362.04.patch
>
>
> {{InvalidateBlocks}} must consistently use datanodeUuid as the key. e.g. add 
> and remove functions use datanode UUID and storage ID.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to