[ https://issues.apache.org/jira/browse/HDDS-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Viswanadham resolved HDDS-2236. -------------------------------------- Resolution: Not A Problem Discussed offline with [~arp], this was an intentional choice to use http.bind.host to 0.0.0.0 so that on multihomed environments/normal clusters it binds to all interfaces. > Remove default http-bind-host from ozone-default.xml > ---------------------------------------------------- > > Key: HDDS-2236 > URL: https://issues.apache.org/jira/browse/HDDS-2236 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Reporter: Bharat Viswanadham > Priority: Major > > Right now, in the code to get HttpBindAddress > > final Optional<String> bindHost = > getHostNameFromConfigKeys(conf, bindHostKey); > final Optional<Integer> addressPort = > getPortNumberFromConfigKeys(conf, addressKey); > final Optional<String> addressHost = > getHostNameFromConfigKeys(conf, addressKey); > String hostName = bindHost.orElse(addressHost.orElse(bindHostDefault)); > return NetUtils.createSocketAddr( > hostName + ":" + addressPort.orElse(bindPortdefault)); > > So, if http-address is mentioned in the config with some hostname, still > bind-host (0.0.0.0) will be used, as ozone-default.xml has value for > http-bind-host with 0.0.0.0. > > Like this, we need to delete the default 0.0.0.0 for recon,freon,datanode. > <property> > <name>ozone.om.http-bind-host</name> > <value>0.0.0.0</value> > <tag>OM, MANAGEMENT</tag> > <description> > The actual address the OM web server will bind to. If this optional > the address is set, it overrides only the hostname portion of > ozone.om.http-address. > </description> -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org