Thanks for the reply Robert – I will try out #1 & keep you posted.
From: Robert Metzger <rmetz...@apache.org>
Date: Wednesday, May 24, 2017 at 7:44 AM
To: "Jain, Ankit" <ankit.j...@here.com>
Cc: "user@flink.apache.org" <user@flink.apache.org>
Subject: R
;>
>>
>>
>> *From: *"Jain, Ankit" <ankit.j...@here.com>
>> *Date: *Tuesday, May 16, 2017 at 12:14 AM
>>
>> *To: *Stephan Ewen <se...@apache.org>, "user@flink.apache.org" <
>> user@flink.apache.org>
>> *Subject:
Date: *Tuesday, May 16, 2017 at 12:14 AM
>
> *To: *Stephan Ewen <se...@apache.org>, "user@flink.apache.org" <
> user@flink.apache.org>
> *Subject: *Re: High Availability on Yarn
>
>
>
> Bringing it back to list’s focus.
>
>
>
> *From: *"
Following up on this.
From: "Jain, Ankit" <ankit.j...@here.com>
Date: Tuesday, May 16, 2017 at 12:14 AM
To: Stephan Ewen <se...@apache.org>, "user@flink.apache.org"
<user@flink.apache.org>
Subject: Re: High Availability on Yarn
Bringing it back to list’
Bringing it back to list’s focus.
From: "Jain, Ankit" <ankit.j...@here.com>
Date: Thursday, May 11, 2017 at 1:19 PM
To: Stephan Ewen <se...@apache.org>, "user@flink.apache.org"
<user@flink.apache.org>
Subject: Re: High Availability on Yarn
Got the answer o
it" <ankit.j...@here.com>
Date: Monday, May 8, 2017 at 9:09 AM
To: Stephan Ewen <se...@apache.org>, "user@flink.apache.org"
<user@flink.apache.org>
Subject: Re: High Availability on Yarn
Thanks Stephan – we will go with a central ZooKeeper Instance and hopef
day, May 8, 2017 at 9:09 AM
To: Stephan Ewen <se...@apache.org>, "user@flink.apache.org"
<user@flink.apache.org>
Subject: Re: High Availability on Yarn
Thanks Stephan – we will go with a central ZooKeeper Instance and hopefully
have it started through a cloudformation scri
;
<ankit.j...@here.com>
Subject: Re: High Availability on Yarn
@Ankit:
ZooKeeper is required in YARN setups still. Even if there is only one
JobManager in the normal case, Yarn can accidentally create a second one when
there is a network partition.
To prevent that this leads to inconsis
;
> *From: *Aljoscha Krettek <aljos...@apache.org>
> *Date: *Thursday, May 4, 2017 at 1:19 AM
> *To: *"Jain, Ankit" <ankit.j...@here.com>
> *Cc: *"user@flink.apache.org" <user@flink.apache.org>, Till Rohrmann <
> trohrm...@apache.org>
&
ave a dedicated Zookeeper instance per flink job?
>
> Thanks
> Ankit
>
> From: Aljoscha Krettek <aljos...@apache.org>
> Date: Thursday, May 4, 2017 at 1:19 AM
> To: "Jain, Ankit" <ankit.j...@here.com>
> Cc: "user@flink.apache.org" <user@flink.apa
rg" <user@flink.apache.org>, Till Rohrmann
<trohrm...@apache.org>
Subject: Re: High Availability on Yarn
Hi,
Yes, for YARN there is only one running JobManager. As far as I Know, In this
case ZooKeeper is only used to keep track of checkpoint metadata and the
execution graph of the
ednesday, May 3, 2017 at 2:05 AM
> To: "Jain, Ankit" <ankit.j...@here.com>
> Cc: "user@flink.apache.org" <user@flink.apache.org>, Till Rohrmann
> <trohrm...@apache.org>
> Subject: Re: High Availability on Yarn
>
> Hi,
> As a first
nkit
From: Aljoscha Krettek <aljos...@apache.org>
Date: Wednesday, May 3, 2017 at 2:05 AM
To: "Jain, Ankit" <ankit.j...@here.com>
Cc: "user@flink.apache.org" <user@flink.apache.org>, Till Rohrmann
<trohrm...@apache.org>
Subject: Re: High Availability on
Hi,
As a first comment, the work mentioned in the FLIP-6 doc you linked is still
work-in-progress. You cannot use these abstractions yet without going into the
code and setting up a cluster “by hand”.
The documentation for one-step deployment of a Job to YARN is available here:
Hi fellow users,
We are trying to straighten out high availability story for flink.
Our setup includes a long running EMR cluster, job submission is a two-step
process – 1) Flink cluster is first created using flink yarn client on the EMR
cluster already running 2) Flink job is submitted.
I
15 matches
Mail list logo
