flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tillrohrmann <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-3184] [timeouts] Decrease timeouts
Date Thu, 17 Dec 2015 18:55:14 GMT
GitHub user tillrohrmann opened a pull request:


    [FLINK-3184] [timeouts] Decrease timeouts

    This PR introduces a client side timeout of 60 s and a cluster side timeout of 10 s. Both
timeouts can be configured via `akka.client.timeout` and `akka.ask.timeout` in the configuration.

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

    $ git pull https://github.com/tillrohrmann/flink decreaseAkkaTimeout

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


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

    This closes #1468
commit 754c0c408d92e931218a137f388fb77f51df964a
Author: Till Rohrmann <trohrmann@apache.org>
Date:   2015-12-15T14:15:12Z

    Harmonize config key for number of retries and retry delay

commit dd81da02ca6eaf8e0e38cf4511e26cb553c71f72
Author: Till Rohrmann <trohrmann@apache.org>
Date:   2015-12-15T16:34:17Z

    Add missing param descriptions to FlinkYarnCluster, remove implicit timeout from ApplicationClient

commit 5e967bf8a9ba066be73905338acfd5deb4894602
Author: Till Rohrmann <trohrmann@apache.org>
Date:   2015-12-15T16:37:20Z

    [FLINK-3184] [timeouts] Set default cluster side timeout to 10 s and the client side timeout
to 60 s.
    Adapt Akka failure detector timings to respect new 10 s Akka ask timeout. Add logging
statements to JobClientActor
    Introduce separation between client and cluster timeout
    Sets the cluster timeout to 10 s and the client timeout to 60 s.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message