[
https://issues.apache.org/jira/browse/HDFS-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-2861:
------------------------------
Attachment: hdfs-2861.txt
Attached patch does the following:
- cleaned up the error messages when configuration isn't properly set up
- improved the code so that, if the dfs.http.address is set to 0.0.0.0, that it
uses the hostname from the RPC address instead (to match the secondary namenode)
- added a sanity check that the IP address stored in the member variable is not
0.0.0.0.
> HA: checkpointing should verify that the dfs.http.address has been configured
> to a non-loopback for peer NN
> -----------------------------------------------------------------------------------------------------------
>
> Key: HDFS-2861
> URL: https://issues.apache.org/jira/browse/HDFS-2861
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Attachments: hdfs-2861.txt
>
>
> In an HA setup I was running for the past week, I just noticed that
> checkpoints weren't getting properly uploaded, since the SBN was connecting
> to http://0.0.0.0:50070/ rather than the correct dfs.http.address. So, it was
> uploading checkpoints to itself instead of the peer. We should add sanity
> checks during startup to ensure that the configuration is correct.
--
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
