[ 
https://issues.apache.org/jira/browse/FLINK-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257176#comment-16257176
 ] 

ASF GitHub Bot commented on FLINK-8099:
---------------------------------------

GitHub user aljoscha opened a pull request:

    https://github.com/apache/flink/pull/5031

    [FLINK-8099] Reduce default restart delay to 1 second

    R: @tillrohrmann 
    
    We could also introduce an extra entry in `ConfigConstants` for the `"1 s"` 
default but I opted against that. What do you think?

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aljoscha/flink jira-8099-1s-delay-restart

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5031.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5031
    
----
commit 6d1d9b1caabfcd731ec2b2ba952fc5a0b27e98e7
Author: Aljoscha Krettek <[email protected]>
Date:   2017-11-17T16:19:51Z

    [FLINK-8099] Reduce default restart delay to 1 second

----


> Reduce default restart delay to 1 second
> ----------------------------------------
>
>                 Key: FLINK-8099
>                 URL: https://issues.apache.org/jira/browse/FLINK-8099
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Blocker
>             Fix For: 1.4.0
>
>
> Currently, when a job fails Flink will wait for 10 seconds until restarting 
> the job. Even zero delay is a reasonable setting but will result in 
> "flooding" the logs and quickly increasing the restart counter because at 
> zero delay you will always see failures when no standby resources are 
> available.
> Reducing this to 1 second should make for a nicer out-of-box experience and 
> not flood too much.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to