flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Ewen <se...@apache.org>
Subject Re: Redeployements and state
Date Fri, 05 Feb 2016 16:39:52 GMT
@Don

In Flink, the client needs not keep running, it can detach itself once the
job is submitted, or stay connected and receive status messages. Since the
client is not necessary for the program execution, I think you don't need
"supervise" or anything like that...

On Mon, Feb 1, 2016 at 7:23 PM, Ufuk Celebi <uce@apache.org> wrote:

>
> > On 01 Feb 2016, at 17:14, Don Frascuchon <frascuchon@gmail.com> wrote:
> >
> > Hi,
> >
> > In reference with this topic, there is any feature for automatically
> restart job after a task exception? Like --supervise command line option in
> apache spark
>
> If you are referring to job manager/task manager instances: No. Currently,
> the recommended way is to run with YARN in order to get this behaviour.
>
> If you are referring to tasks: you can enable this via the ExecutionConfig
> (
> https://ci.apache.org/projects/flink/flink-docs-master/apis/batch/index.html#execution-configuration)
> via setNumberOfExecutionRetries() and setExecutionRetryDelay().
>
> Does this help?
>
> – Ufuk
>
>

Mime
View raw message