Kevin,

I think specifying datanode.dns.interface alone for dfs and mapred is enough
(not sure). You only have to set it to eth0 or eth1, etc

J-D

On Sat, Sep 6, 2008 at 7:18 PM, Kevin <[EMAIL PROTECTED]> wrote:

> Hi J-D,
>
> I could not try it right now as I am not familiar with setting up DNS
> server (I assume the parameters you mentioned are those specifying DNS
> server). It actually becomes more interesting as why specifying the IP
> does not suffice? Do you mean that hadoop will decide the right IP of
> a node by its own, instead of sticking to the default one?
>
> -Kevin
>
>
>
> On Fri, Sep 5, 2008 at 8:45 PM, Jean-Daniel Cryans <[EMAIL PROTECTED]>
> wrote:
> > Kevin,
> >
> > Did you try changing the
> >
> dfs.datanode.dns.interface/dfs.datanode.dns.nameserver/mapred.tasktracker.dns.interface/mapred.tasktracker.dns.nameserver
> > parameters?
> >
> > J-D
> >
> > On Fri, Sep 5, 2008 at 8:14 PM, Kevin <[EMAIL PROTECTED]> wrote:
> >
> >> Hi,
> >>
> >> The machines I am using each has multiple network cards, and hence
> >> multiple IP addresses. Some of them look like a default IP. However, I
> >> wish to use some other IPs, and tried to modify the hadoop-site.xml,
> >> masters, and slaves files. But it looks that the IP still jumps to the
> >> default ones when hadoop runs. Does anyone have an idea how I could
> >> possibly make it work? Thank you!
> >>
> >> -Kevin
> >>
> >
>

Reply via email to