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

Jakob Homan updated HDFS-1080:
------------------------------

    Attachment: HDFS-1080-trunk-1.patch

Updated patch per Konstantin's comments. Checkpointer needed a bit more work to 
get the relevant information to the right to the needed function, but should 
work exactly the same.  I'm going to open a JIRA to combine this code 
duplication until the 2ndarryNN is removed.  

Konstantin pointed out that this will be an incompatible change in that, were 
one specifying localhost as the 2nd/CP Nodes' address and relying on that value 
to be resolved on the node.  For now on, one will need to specify the exact 
address to use, which is much more correct in my opinion, particularly on 
production systems that may rely on IP aliasing.  I'll mark this as 
incompatible.

> SecondaryNameNode image transfer should use the defined http address rather 
> than local ip address
> -------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1080
>                 URL: https://issues.apache.org/jira/browse/HDFS-1080
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>         Attachments: HDFS-1080-trunk-1.patch, HDFS-1080-trunk.patch, 
> HDFS-1080-Y20.patch
>
>
> Currently when telling the NN where to get the merged image, SNN uses 
> getLocalHost.getAddr(), which may not return the correct ip addr.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to