[SPARK-54794][CORE] Suppress verbose FsHistoryProvider.checkForLogs scanning logs
#53555
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
HyukjinKwon
approved these changes
Dec 22, 2025
Member
Author
|
Thank you, @HyukjinKwon ! |
sarutak
approved these changes
Dec 22, 2025
Member
|
Merged to |
sarutak
pushed a commit
that referenced
this pull request
Dec 22, 2025
… scanning logs ### What changes were proposed in this pull request? This PR aims to suppress verbose `FsHistoryProvider.checkForLogs` scanning logs. ### Why are the changes needed? This is a kind of regression at Apache Spark 4.1.0 switched from `logDebug` to `logInfo` accidentally. We had better recover them back to `DEBUG` level because it's excessively verbose currently. - #52382 ``` 25/12/21 22:27:53 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356063285 25/12/21 22:28:03 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356073312 25/12/21 22:28:13 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356083338 25/12/21 22:28:23 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356093347 25/12/21 22:28:33 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356103369 25/12/21 22:28:43 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356113391 25/12/21 22:28:53 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356123402 25/12/21 22:29:03 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356133422 25/12/21 22:29:13 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356143443 25/12/21 22:29:23 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356153458 25/12/21 22:29:33 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356163471 25/12/21 22:29:43 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356173491 25/12/21 22:29:53 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356183502 25/12/21 22:30:03 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356193517 25/12/21 22:30:13 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356203529 25/12/21 22:30:23 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356213555 25/12/21 22:30:33 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356223567 25/12/21 22:30:43 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356233585 25/12/21 22:30:53 INFO FsHistoryProvider: Scanning s3a://spark-events with lastScanTime=1766356243599 ``` ### Does this PR introduce _any_ user-facing change? No behavior change except log message level. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #53555 from dongjoon-hyun/SPARK-54794. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Kousuke Saruta <sarutak@apache.org> (cherry picked from commit d0fbb15) Signed-off-by: Kousuke Saruta <sarutak@apache.org>
Member
Author
|
Thank you, @sarutak . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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 suppress verbose
FsHistoryProvider.checkForLogsscanning logs.Why are the changes needed?
This is a kind of regression at Apache Spark 4.1.0 switched from
logDebugtologInfoaccidentally. We had better recover them back toDEBUGlevel because it's excessively verbose currently.Does this PR introduce any user-facing change?
No behavior change except log message level.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.