Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: 
 <CAFAd71VLwq4DwOdkZioUKWyiCs-aDm=vV43cVgMFE1NqXV95yQ@mail.gmail.com>
References: 
 <CAFAd71VLwq4DwOdkZioUKWyiCs-aDm=vV43cVgMFE1NqXV95yQ@mail.gmail.com>
From: Namikaze Minato <lloydsensei@gmail.com>
Date: Tue, 8 Dec 2015 12:18:01 +0100
Message-ID: 
 <CACmJb3xWWjO_UA0VrH5Tz_afx8=p9mdPPvM3hg4yE=aLu9Jt0A@mail.gmail.com>
Subject: Re: nodemanager listen on 0.0.0.0
To: Li Li <fancyerii@gmail.com>
Cc: user@hadoop.apache.org
Content-Type: text/plain; charset=UTF-8

Listening on 0.0.0.0 means listening on all interfaces. Do you really
NEED to have it listen only on internal addresses? If you're not
connected to a public network it should not matter, right?

Anyway, your cluster should work as-is.

Regards,
LLoyd

PS: FYI, your e-mail ended up in spams.

On 8 December 2015 at 10:27, Li Li <fancyerii@gmail.com> wrote:
>    I want to setup a yarn cluster. It's not allowed to visit from
> public network so I changed many configuration files to let all
> service bind to the internal network address.
>    All thing is fine exception the nodemanager which bind
> 0.0.0.0:13562. I searched the default-mapred-default.xml and found it
> mapreduce.shuffle.port.
>    Which configuration file should I change to let nodemanager listen
> on internal address instead of 0.0.0.0?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: user-help@hadoop.apache.org
>

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