[
https://issues.apache.org/jira/browse/HDFS-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins updated HDFS-3216:
------------------------------
Attachment: hdfs-3216.txt
#1 We still need the notion of canonical IP, mostly for cases that don't care
about multiple IP addresses. Updated the javadoc.
#2 Yes, when reading/writing DatanodeInfos to/from streams (same as before when
creating a DatanodeID w/o a name)
#3 Done
#4 It's tested by TestWebHdfsFileSystemContract#testGetFileBlockLocations. It
currently only tests the first IP vs the whole array since LocatedBlock (HDFS)
is multi-IP aware but BlockLocation (common) is not. Fixed the cast, now casts
to String and serializes/deserializes the IPs, the test does check this (was
failing now passes).
#5 We expect this field to always contain IPs, see HDFS-3144, we no longer
overload this field. Filed HDFS-3230 to cleanup the tests, will do it on trunk
since its independent of this change.
> DatanodeID should support multiple IP addresses
> -----------------------------------------------
>
> Key: HDFS-3216
> URL: https://issues.apache.org/jira/browse/HDFS-3216
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hdfs-3216.txt, hdfs-3216.txt
>
>
> The DatanodeID has a single field for the IP address, for HDFS-3146 we need
> to extend it to support multiple addresses.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
