hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12532) DN Reg can Fail when principal doesn't contain hostname and floatingIP is configured.
Date Mon, 25 Sep 2017 19:53:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179666#comment-16179666

Daryn Sharp commented on HDFS-12532:

bq.  Floating IP configured for HA purpose.Such that Active and standby can use same IP to
access webUI.
bq. Here datanode registered with X.Y.Y.1 and X.Y.Y.100 is floating IP which is used for further
communication which will fail.

Ok.  You're using ip failover, like we also do.  The stack trace shows that:
# The NN is "X.Y.Z.1".
# The NN sees the DN connection from "X.Y.Y.100"
# The DN's registration is self-identifying as "X.Y.Y.1"
# The DN's BP id contains "X.Y.Y.1" which should be the NN's ip...

This tells me the DN is running on the NN.  "X.Y.Z.1" doesn't exist.

The floating ip "X.Y.Y.100" is the interface ip, "X.Y.Y.1" is ip aliased to it which is why
non-explicitly bound connections from the DN originate from "X.Y.Y.100".  (In practice you'll
probably want the opposite, ie. your floating ip to be aliased, which would incidentally "fix"
your issue)

Binding to loopback per the proposal only works when the DN is running on the NN.  It won't
work if the hosts are different.

bq. I also not keen on having more confs w/o having a clearly stated use case.
Ok, then we can make it configurable..?

No.  This appears to be a self-inflicted injury in perhaps a test environment.  I recommend
either switching your interface and aliased ips, or set {{dfs.namenode.datanode.registration.ip-hostname-check=false}}.

> DN Reg can Fail when principal doesn't contain hostname and floatingIP is configured.
> -------------------------------------------------------------------------------------
>                 Key: HDFS-12532
>                 URL: https://issues.apache.org/jira/browse/HDFS-12532
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Brahma Reddy Battula
>            Assignee: Brahma Reddy Battula
> Configure principal without hostname (i.e hdfs/hadoop@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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message