Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Duplicate
-
2.1.0
-
None
-
None
Description
Today, when we miss a trigger interval we wait until the next one to fire. However, for real workloads this usually means that you fall further and further behind by sitting idle while waiting. We should revisit this decision.
Attachments
Issue Links
- duplicates
-
SPARK-20209 Execute next trigger immediately if previous batch took longer than trigger interval
- Resolved