[
https://issues.apache.org/jira/browse/HDFS-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HDFS-7225:
------------------------------------------
Labels: 2.6.1-candidate (was: )
This wasn't originally in 2.6.1, must have been committed to 2.6, which was
already 2.6.2. I just committed this to 2.6.1 taking [~sjlee0] cherry-pick,
which must have come from branch-2.6.
Ran compilation and TestComputeInvalidateWork before the push.
> Remove stale block invalidation work when DN re-registers with different UUID
> -----------------------------------------------------------------------------
>
> Key: HDFS-7225
> URL: https://issues.apache.org/jira/browse/HDFS-7225
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.6.0
> Reporter: Zhe Zhang
> Assignee: Zhe Zhang
> Labels: 2.6.1-candidate
> Fix For: 2.7.0, 2.6.1
>
> Attachments: HDFS-7225-v1.patch, HDFS-7225-v2.patch,
> HDFS-7225-v3.patch, HDFS-7225.004.patch, HDFS-7225.005.patch
>
>
> {{BlockManager#invalidateWorkForOneNode}} looks up a DataNode by the
> {{datanodeUuid}} and passes the resultant {{DatanodeDescriptor}} to
> {{InvalidateBlocks#invalidateWork}}. However, if a wrong or outdated
> {{datanodeUuid}} is used, a null pointer will be passed to {{invalidateWork}}
> which will use it to lookup in a {{TreeMap}}. Since the key type is
> {{DatanodeDescriptor}}, key comparison is based on the IP address. A null key
> will crash the NameNode with an NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
