[
https://issues.apache.org/jira/browse/HDFS-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron T. Myers updated HDFS-3404:
---------------------------------
Attachment: HDFS-3404.patch
Here's an initial patch to make sure folks are OK with the approach. I'm still
mulling over how best to write tests for this, which is a tad difficult on a
single-node machine.
I tested this manually by setting up an HA setup where each NN itself binds to
0.0.0.0, but has actual addresses for the other NN. It worked as expected.
> Make putImage in GetImageServlet infer remote address to fetch from
> -------------------------------------------------------------------
>
> Key: HDFS-3404
> URL: https://issues.apache.org/jira/browse/HDFS-3404
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: HDFS-3404.patch
>
>
> As it stands, daemons which perform checkpointing must determine their own
> address on which they can be reached, so that the NN which they checkpoint
> against knows what address to fetch a merged fsimage from. This causes
> problems if, for example, the daemon performing checkpointing binds to
> 0.0.0.0, and thus can't be sure of what address the NN can reach it at.
--
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
