[jira] [Updated] (HDFS-6362) InvalidateBlocks is inconsistent in usage of DatanodeUuid and StorageID

2014-05-16 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HDFS-6362:


Attachment: HDFS-6362.01.patch

Patch for Jenkins run.

 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
 Attachments: HDFS-6362.01.patch, HDFS-6362.02.patch


 {{InvalidateBlocks}} must consistently use datanodeUuid as the key.



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

[jira] [Updated] (HDFS-6362) InvalidateBlocks is inconsistent in usage of DatanodeUuid and StorageID

2014-05-16 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HDFS-6362:


   Resolution: Fixed
Fix Version/s: 2.4.1
   3.0.0
   Status: Resolved  (was: Patch Available)

I committed this to trunk, branch-2 and branch-2.4.

The merge to branch-2 was unexpectedly complex due to code divergence between 
trunk and branch-2. I also merged down HDFS-4052 to reduce the divergence 
between the branches.

Thanks for the review [~cnauroth].

 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)

[jira] [Updated] (HDFS-6362) InvalidateBlocks is inconsistent in usage of DatanodeUuid and StorageID

2014-05-15 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HDFS-6362:


Attachment: HDFS-6362.04.patch

Rebase patch to resolve conflicts with HDFS-6186.

 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
 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)

[jira] [Updated] (HDFS-6362) InvalidateBlocks is inconsistent in usage of DatanodeUuid and StorageID

2014-05-15 Thread Chris Nauroth (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Nauroth updated HDFS-6362:


Hadoop Flags: Reviewed

+1 for the patch.  Thank you for fixing this, Arpit.

 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
 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)

[jira] [Updated] (HDFS-6362) InvalidateBlocks is inconsistent in usage of DatanodeUuid and StorageID

2014-05-11 Thread Arpit Agarwal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HDFS-6362:


Attachment: HDFS-6362.03.patch

Fix findbugs warning.

 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
 Attachments: HDFS-6362.01.patch, HDFS-6362.02.patch, 
 HDFS-6362.03.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)