You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by Tao Xiao <xi...@gmail.com> on 2014/12/18 15:24:03 UTC
How to let namenode http web UI port listen on another interface?
I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
(10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
is configured as 50070.
Command "netstat -apn | grep 50070" returns the following results：
tcp 0 0 10.252.25.68:50070 0.0.0.0:*
LISTEN 27159/java
tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
TIME_WAIT -
So port 50070 seems to be listening on eth0 and I can not access namenode
http web console by eth1.
I'd like to know how to let port 50070 listen on eth1. I suppose that can
be down by modifying Jetty's configuration - Jetty is namenode's web
server, but I'm not sure how to do that.
Thanks in advance.
Re: How to let namenode http web UI port listen on another interface?
Posted by Tao Xiao <xi...@gmail.com>.
That works for me, thank you Susheel.
But this causes one more problem - Cloudera manager can not communicate
with namenode as shown here <http://imagebin.ca/v/1lBFO2Sh51WV>. It seems
cloudera's service monitor does not know that namenode's http address is
changed.
Perhaps I should move this post to scm-users@cloudera.org
2014-12-19 17:05 GMT+08:00 Susheel Kumar Gadalay <sk...@gmail.com>:
>
> Try giving this property in hdfs-site.xml
>
> dfs.namenode.http-address=0.0.0.0:50070
>
> Replace 0.0.0.0 with your other network interface.
>
> On 12/18/14, Tao Xiao <xi...@gmail.com> wrote:
> > I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
> > (10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
> > is configured as 50070.
> >
> > Command "netstat -apn | grep 50070" returns the following results：
> > tcp 0 0 10.252.25.68:50070 0.0.0.0:*
> > LISTEN 27159/java
> > tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
> > TIME_WAIT -
> >
> >
> > So port 50070 seems to be listening on eth0 and I can not access namenode
> > http web console by eth1.
> >
> > I'd like to know how to let port 50070 listen on eth1. I suppose that can
> > be down by modifying Jetty's configuration - Jetty is namenode's web
> > server, but I'm not sure how to do that.
> >
> > Thanks in advance.
> >
>
Re: How to let namenode http web UI port listen on another interface?
Posted by Tao Xiao <xi...@gmail.com>.
That works for me, thank you Susheel.
But this causes one more problem - Cloudera manager can not communicate
with namenode as shown here <http://imagebin.ca/v/1lBFO2Sh51WV>. It seems
cloudera's service monitor does not know that namenode's http address is
changed.
Perhaps I should move this post to scm-users@cloudera.org
2014-12-19 17:05 GMT+08:00 Susheel Kumar Gadalay <sk...@gmail.com>:
>
> Try giving this property in hdfs-site.xml
>
> dfs.namenode.http-address=0.0.0.0:50070
>
> Replace 0.0.0.0 with your other network interface.
>
> On 12/18/14, Tao Xiao <xi...@gmail.com> wrote:
> > I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
> > (10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
> > is configured as 50070.
> >
> > Command "netstat -apn | grep 50070" returns the following results：
> > tcp 0 0 10.252.25.68:50070 0.0.0.0:*
> > LISTEN 27159/java
> > tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
> > TIME_WAIT -
> >
> >
> > So port 50070 seems to be listening on eth0 and I can not access namenode
> > http web console by eth1.
> >
> > I'd like to know how to let port 50070 listen on eth1. I suppose that can
> > be down by modifying Jetty's configuration - Jetty is namenode's web
> > server, but I'm not sure how to do that.
> >
> > Thanks in advance.
> >
>
Re: How to let namenode http web UI port listen on another interface?
Posted by Tao Xiao <xi...@gmail.com>.
That works for me, thank you Susheel.
But this causes one more problem - Cloudera manager can not communicate
with namenode as shown here <http://imagebin.ca/v/1lBFO2Sh51WV>. It seems
cloudera's service monitor does not know that namenode's http address is
changed.
Perhaps I should move this post to scm-users@cloudera.org
2014-12-19 17:05 GMT+08:00 Susheel Kumar Gadalay <sk...@gmail.com>:
>
> Try giving this property in hdfs-site.xml
>
> dfs.namenode.http-address=0.0.0.0:50070
>
> Replace 0.0.0.0 with your other network interface.
>
> On 12/18/14, Tao Xiao <xi...@gmail.com> wrote:
> > I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
> > (10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
> > is configured as 50070.
> >
> > Command "netstat -apn | grep 50070" returns the following results：
> > tcp 0 0 10.252.25.68:50070 0.0.0.0:*
> > LISTEN 27159/java
> > tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
> > TIME_WAIT -
> >
> >
> > So port 50070 seems to be listening on eth0 and I can not access namenode
> > http web console by eth1.
> >
> > I'd like to know how to let port 50070 listen on eth1. I suppose that can
> > be down by modifying Jetty's configuration - Jetty is namenode's web
> > server, but I'm not sure how to do that.
> >
> > Thanks in advance.
> >
>
Re: How to let namenode http web UI port listen on another interface?
Posted by Tao Xiao <xi...@gmail.com>.
That works for me, thank you Susheel.
But this causes one more problem - Cloudera manager can not communicate
with namenode as shown here <http://imagebin.ca/v/1lBFO2Sh51WV>. It seems
cloudera's service monitor does not know that namenode's http address is
changed.
Perhaps I should move this post to scm-users@cloudera.org
2014-12-19 17:05 GMT+08:00 Susheel Kumar Gadalay <sk...@gmail.com>:
>
> Try giving this property in hdfs-site.xml
>
> dfs.namenode.http-address=0.0.0.0:50070
>
> Replace 0.0.0.0 with your other network interface.
>
> On 12/18/14, Tao Xiao <xi...@gmail.com> wrote:
> > I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
> > (10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
> > is configured as 50070.
> >
> > Command "netstat -apn | grep 50070" returns the following results：
> > tcp 0 0 10.252.25.68:50070 0.0.0.0:*
> > LISTEN 27159/java
> > tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
> > TIME_WAIT -
> >
> >
> > So port 50070 seems to be listening on eth0 and I can not access namenode
> > http web console by eth1.
> >
> > I'd like to know how to let port 50070 listen on eth1. I suppose that can
> > be down by modifying Jetty's configuration - Jetty is namenode's web
> > server, but I'm not sure how to do that.
> >
> > Thanks in advance.
> >
>
Re: How to let namenode http web UI port listen on another interface?
Posted by Susheel Kumar Gadalay <sk...@gmail.com>.
Try giving this property in hdfs-site.xml
dfs.namenode.http-address=0.0.0.0:50070
Replace 0.0.0.0 with your other network interface.
On 12/18/14, Tao Xiao <xi...@gmail.com> wrote:
> I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
> (10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
> is configured as 50070.
>
> Command "netstat -apn | grep 50070" returns the following results：
> tcp 0 0 10.252.25.68:50070 0.0.0.0:*
> LISTEN 27159/java
> tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
> TIME_WAIT -
>
>
> So port 50070 seems to be listening on eth0 and I can not access namenode
> http web console by eth1.
>
> I'd like to know how to let port 50070 listen on eth1. I suppose that can
> be down by modifying Jetty's configuration - Jetty is namenode's web
> server, but I'm not sure how to do that.
>
> Thanks in advance.
>
Re: How to let namenode http web UI port listen on another interface?
Posted by Susheel Kumar Gadalay <sk...@gmail.com>.
Try giving this property in hdfs-site.xml
dfs.namenode.http-address=0.0.0.0:50070
Replace 0.0.0.0 with your other network interface.
On 12/18/14, Tao Xiao <xi...@gmail.com> wrote:
> I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
> (10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
> is configured as 50070.
>
> Command "netstat -apn | grep 50070" returns the following results：
> tcp 0 0 10.252.25.68:50070 0.0.0.0:*
> LISTEN 27159/java
> tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
> TIME_WAIT -
>
>
> So port 50070 seems to be listening on eth0 and I can not access namenode
> http web console by eth1.
>
> I'd like to know how to let port 50070 listen on eth1. I suppose that can
> be down by modifying Jetty's configuration - Jetty is namenode's web
> server, but I'm not sure how to do that.
>
> Thanks in advance.
>
Re: How to let namenode http web UI port listen on another interface?
Posted by Susheel Kumar Gadalay <sk...@gmail.com>.
Try giving this property in hdfs-site.xml
dfs.namenode.http-address=0.0.0.0:50070
Replace 0.0.0.0 with your other network interface.
On 12/18/14, Tao Xiao <xi...@gmail.com> wrote:
> I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
> (10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
> is configured as 50070.
>
> Command "netstat -apn | grep 50070" returns the following results：
> tcp 0 0 10.252.25.68:50070 0.0.0.0:*
> LISTEN 27159/java
> tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
> TIME_WAIT -
>
>
> So port 50070 seems to be listening on eth0 and I can not access namenode
> http web console by eth1.
>
> I'd like to know how to let port 50070 listen on eth1. I suppose that can
> be down by modifying Jetty's configuration - Jetty is namenode's web
> server, but I'm not sure how to do that.
>
> Thanks in advance.
>
Re: How to let namenode http web UI port listen on another interface?
Posted by Susheel Kumar Gadalay <sk...@gmail.com>.
Try giving this property in hdfs-site.xml
dfs.namenode.http-address=0.0.0.0:50070
Replace 0.0.0.0 with your other network interface.
On 12/18/14, Tao Xiao <xi...@gmail.com> wrote:
> I installed HDFS (CDH 5.2.1) on a host with two interfaces - eth0
> (10.252.25.68) and eth1 (120.27.43.80). Namenode http web ui port
> is configured as 50070.
>
> Command "netstat -apn | grep 50070" returns the following results：
> tcp 0 0 10.252.25.68:50070 0.0.0.0:*
> LISTEN 27159/java
> tcp 0 0 10.252.25.68:50070 10.252.25.68:44871
> TIME_WAIT -
>
>
> So port 50070 seems to be listening on eth0 and I can not access namenode
> http web console by eth1.
>
> I'd like to know how to let port 50070 listen on eth1. I suppose that can
> be down by modifying Jetty's configuration - Jetty is namenode's web
> server, but I'm not sure how to do that.
>
> Thanks in advance.
>