[SPARK-52456][CORE] Lower the minimum limit of spark.eventLog.rolling.maxFileSize
#51162
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dongjoon-hyun
changed the title
spark.eventLog.rolling.maxFileSize
dongjoon-hyun
force-pushed
the
SPARK-52456
branch
from
28d2bea to
c356b1a
Compare
yaooqinn
approved these changes
Jun 12, 2025
Member
Author
|
Thank you, @yaooqinn . Merged to master for Apache Spark 4.1.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to lower the minimum limit of
spark.eventLog.rolling.maxFileSizefrom10MiBto2MiBat Apache Spark 4.1.0 while keeping the default (128MiB).Why are the changes needed?
spark.eventLog.rolling.maxFileSizehas10MiBas the lower bound limit since Apache Spark 3.0.0.By reducing the lower bound to
2MiB, we can allow Spark jobs to write small log files more frequently and faster without waiting for10MiB. This is helpful some slow(large micro-batch period) or low-traffic streaming jobs. The users will set a proper value for their jobs.Does this PR introduce any user-facing change?
There is no behavior change for the existing jobs. This only extends the range of configuration values for a user who wants to have lower values.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.