GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/17525
[SPARK-20209][SS] Execute next trigger immediately if previous batch took
longer than trigger interval
## What changes were proposed in this pull request?
For large trigger intervals (e.g. 10 minutes), if a batch takes 11 minutes,
then it will wait for 9 mins before starting the next batch. This does not make
sense. The processing time based trigger policy should be to do process batches
as fast as possible, but no faster than 1 in every trigger interval. If batches
are taking longer than trigger interval anyways, then no point waiting extra
trigger interval.
In this PR, I modified the ProcessingTimeExecutor to do so.
## How was this patch tested?
Added new unit tests to comprehensively test this behavior.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdas/spark SPARK-20209
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/17525.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 #17525
----
commit 50f0195a4eee34db813c9040437de95796c577cc
Author: Tathagata Das <tathagata.das1...@gmail.com>
Date: 2017-04-04T06:48:00Z
Removed delay from trigger executor
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
