[ https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730259#comment-13730259 ]
Allen Wittenauer commented on HDFS-5055: ---------------------------------------- So it looks like either HDFS-3404 needs to get rolled back or HDFS-3405 needs to get fixed. As it stands, users can't use certain types of VIPs with the 2NN. > nn->2nn ignores dfs.namenode.secondary.http-address > --------------------------------------------------- > > Key: HDFS-5055 > URL: https://issues.apache.org/jira/browse/HDFS-5055 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.1.0-beta > Reporter: Allen Wittenauer > Priority: Blocker > > The primary namenode attempts to connect back to (incoming hostname):port > regardless of how dfs.namenode.secondary.http-address is configured. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira