[ https://issues.apache.org/jira/browse/HADOOP-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334920#comment-16334920 ]
Daryn Sharp commented on HADOOP-15175: -------------------------------------- bq. Usecase for the floating IP is to provide HA for a Service. Active service will bind to floating IP. Understood. We use a floating IP for all HA. The issue in this case is the floating address is apparently used for routing outbound client connections. That's a system level config that I'm not sure hadoop should be responsible for solving. The original use case was essentially "I want a universal package to deploy everywhere" which contradicts adding a conf for a system specific ip. The local bind address is not random and should be determined by the routing table. Can you change the system's default route to use the specific interface/alias that you need? Or at least add a route for the NN using the interface you need? I'm hesitant to add another conf for a niche case that is better configured by the system. > DN Reg can Fail when principal doesn't contain hostname and floatingIP is > configured. > ------------------------------------------------------------------------------------- > > Key: HADOOP-15175 > URL: https://issues.apache.org/jira/browse/HADOOP-15175 > Project: Hadoop Common > Issue Type: Bug > Reporter: Brahma Reddy Battula > Assignee: Brahma Reddy Battula > Priority: Major > Attachments: HADOOP-15175-002.patch, HDFS-12532.patch > > > Configure principal without hostname (i.e hdfs/had...@hadoop.com) > Configure floatingIP > Start Cluster. > Here DN will fail to register as it can take IP which is not in "/etc/hosts". -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org