_
From: Navina Ramesh
[nram...@linkedin.com.INVALID<mailto:nram...@linkedin.com.INVALID><mailto:nram...@linkedin.com.INVALID>]
Sent: Thursday, July 30, 2015 8:40 PM
To:
dev@samza.apache.org<mailto:dev@samza.apache.org><mailto:dev@samza.apache.org><ma
f we can't get a
>
>
> better
>
>
> address for the AM from YARN, we could at least filter the addresses we
>
>
> get
>
>
> back from the JVM to exclude loopbacks.
>
> -Tommy
>
> From: Navina Ramesh [nram
edin.com.INVALID<mailto:nram...@linkedin.com.INVALID>]
Sent: Thursday, July 30, 2015 8:40 PM
To: dev@samza.apache.org<mailto:dev@samza.apache.org>
Subject: Re: Coordinator URL always 127.0.0.1
Hi Tommy,
Yi is right. Container start is coordinated by the AppMaster using an
NMClient. Container host
iner to the
>> AM,
>> > > it sounds like you're saying it's in the other direction only? Don't
>> > > containers heartbeat to the AM? Regardless, even if we can't get a
>> > better
>> > > address for the AM from YARN, we could at
dress for the AM from YARN, we could at least filter the addresses we
> > get
> > > back from the JVM to exclude loopbacks.
> > >
> > > -Tommy
> > >
> > > From: Navina Ramesh [nram...@linkedin.com.INVALID]
at 5:55 PM, Thomas Becker
> > wrote:
> > >>
> > >> > Ok, I thought there was some communication from the container to the
> > AM,
> > >> > it sounds like you're saying it's in the other direction only?
> Don't
> > >&g
#x27;re saying it's in the other direction only? Don't
> >> > containers heartbeat to the AM? Regardless, even if we can't get a
> >> better
> >> > address for the AM from YARN, we could at least filter the addresses
> we
> >> get
> >> > ba
AM? Regardless, even if we can't get a
>> better
>> > address for the AM from YARN, we could at least filter the addresses we
>> get
>> > back from the JVM to exclude loopbacks.
>> >
>> > -Tommy
>> >
>> > From: Navina Ram
s.
> >
> > -Tommy
> >
> > From: Navina Ramesh [nram...@linkedin.com.INVALID]
> > Sent: Thursday, July 30, 2015 8:40 PM
> > To: dev@samza.apache.org
> > Subject: Re: Coordinator URL always 127.0.0.1
> >
> > Hi
esses we get
> back from the JVM to exclude loopbacks.
>
> -Tommy
>
> From: Navina Ramesh [nram...@linkedin.com.INVALID]
> Sent: Thursday, July 30, 2015 8:40 PM
> To: dev@samza.apache.org
> Subject: Re: Coordinator URL always 1
the addresses we get back from the JVM
to exclude loopbacks.
-Tommy
From: Navina Ramesh [nram...@linkedin.com.INVALID]
Sent: Thursday, July 30, 2015 8:40 PM
To: dev@samza.apache.org
Subject: Re: Coordinator URL always 127.0.0.1
Hi Tommy,
Yi is right
; > them. Can we do something more robust here? How does the container
> > communicate status to the AM?
> >
> > -Tommy
> >
> > ________
> > From: Yi Pan [nickpa...@gmail.com]
> > Sent: Thursday, July 30, 2015 6:48 PM
> &
something more robust here? How does the container
> communicate status to the AM?
>
> -Tommy
>
>
> From: Yi Pan [nickpa...@gmail.com]
> Sent: Thursday, July 30, 2015 6:48 PM
> To: dev@samza.apache.org
> Subject: Re: Coordinator UR
6:48 PM
To: dev@samza.apache.org
Subject: Re: Coordinator URL always 127.0.0.1
Hi, Tommy,
I think that it might be a commonly asked question regarding to multiple
IPs on a single host. A common trick w/o changing code is (copied from SO:
http://stackoverflow.com/questions/2381316/java-inetad
Hi, Tommy,
I think that it might be a commonly asked question regarding to multiple
IPs on a single host. A common trick w/o changing code is (copied from SO:
http://stackoverflow.com/questions/2381316/java-inetaddress-getlocalhost-returns-127-0-0-1-how-to-get-real-ip
)
{code}
1.
Find you
15 matches
Mail list logo
