Github user tdas commented on the issue:
https://github.com/apache/spark/pull/12026
Hi @liyintang, thanks for this PR. I apologize for not providing feedback
on this earlier. This is indeed a practical problem in production, but I am not
sure how adding the jitter would be affect downstream stuff - rate calculation,
flow control, etc. Spark Streaming was not designed keep such things in mind.
In the new Structured Streaming, this would not be a problem, as the batch
interval (called trigger interval there) is optional, and if it is not
specified, it will start next batch when previous batch finishes. That means
that multiple jobs wont synchronize. I suggest you try out Structured
Streaming.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
