Skip to content

Dynamic Batch Interval Adjustment #16993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

zhangqiang2
Copy link

The current Spark Streaming version cannot support the change of batch interval at runtime, given that the speed of input data streams may not highly dynamic from current Internet applications. If we have to do so, one must stop the program first, modify the corresponding code, and then restart the program. However, this will interrupt the execution of entire program, and may cause the data loss. Towards this end, our contribution is to implement a Dynamic Batch Interval Adjustment functionality that can help change the batch interval size at runtime.

This functionality contains two algorithms. One is dynamic adjustment, and the other is static adjustment. The former can predict the size of input data stream and as a result the processing time, by using the most recent processing time and used batch interval. In this way, one can decide whether the batch interval needs to be changed or not, to avoid the data backlog, and secure the system stability. On the other hand, the static adjustment needs the user to manually change the configuration file.

JIRA Issue: https://issues.apache.org/jira/browse/SPARK-19663
My report: https://github.com/floatingtony/System-Lever-Optimization-of-Spark-Streaming

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Feb 19, 2017

Please read http://spark.apache.org/contributing.html and start not with code but with a design doc. However, this has been discussed before on JIRA too IIRC and rejected.

@maropu maropu mentioned this pull request Apr 23, 2017
maropu added a commit to maropu/spark that referenced this pull request Apr 23, 2017
@asfgit asfgit closed this in e9f9715 Apr 24, 2017
peter-toth pushed a commit to peter-toth/spark that referenced this pull request Oct 6, 2018
This pr proposed to close stale PRs. Currently, we have 400+ open PRs and there are some stale PRs whose JIRA tickets have been already closed and whose JIRA tickets does not exist (also, they seem not to be minor issues).

// Open PRs whose JIRA tickets have been already closed
Closes apache#11785
Closes apache#13027
Closes apache#13614
Closes apache#13761
Closes apache#15197
Closes apache#14006
Closes apache#12576
Closes apache#15447
Closes apache#13259
Closes apache#15616
Closes apache#14473
Closes apache#16638
Closes apache#16146
Closes apache#17269
Closes apache#17313
Closes apache#17418
Closes apache#17485
Closes apache#17551
Closes apache#17463
Closes apache#17625

// Open PRs whose JIRA tickets does not exist and they are not minor issues
Closes apache#10739
Closes apache#15193
Closes apache#15344
Closes apache#14804
Closes apache#16993
Closes apache#17040
Closes apache#15180
Closes apache#17238

N/A

Author: Takeshi Yamamuro <yamamuro@apache.org>

Closes apache#17734 from maropu/resolved_pr.

Change-Id: Id2e590aa7283fe5ac01424d30a40df06da6098b5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants