[SPARK-54772][Shuffle] Introduce failedChunks metrics in ChunkFetchHandler #53538
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
Contributor
Author
|
@LuciferYang Can you help review? |
leixm
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Introduce failedChunks metrics in ChunkFetchHandler.
Why are the changes needed?
ChunkFetchHandler often processes ChunkFetchRequests slowly for various reasons, Client may close the connection. When ChunkFetchRequest returns a response to the client, it will print an error log (code). we can introduce a new metric to discover this problem more intuitively
Does this PR introduce any user-facing change?
No.
How was this patch tested?
UTs.
Was this patch authored or co-authored using generative AI tooling?
No.