AngersZhuuuu opened a new pull request, #53594: URL: https://github.com/apache/spark/pull/53594
### What changes were proposed in this pull request? Spark jobs driver side some times show below message ``` java.lang.OutOfMemoryError: GC overhead limit exceeded ``` But Spark executor page didn't show driver GC metrics, When Driver GC is heavy, all executors may be waiting for scheduling, resulting in wasted resources. We need to optimize for heavy GC scenarios. We need to know this information very easily. We can add it <img width="1728" height="528" alt="截屏2025-12-24 17 52 44" src="https://github.com/user-attachments/assets/4ff725e5-c38a-488e-b19f-e4df2b816ef7"; /> ### Why are the changes needed? To help users better understand their assignments ### Does this PR introduce _any_ user-facing change? User can know driver side gc time in executors page ### How was this patch tested? **Before** <img width="1728" height="528" alt="截屏2025-12-24 17 52 44" src="https://github.com/user-attachments/assets/4ff725e5-c38a-488e-b19f-e4df2b816ef7"; /> **After** <img width="1721" height="495" alt="截屏2025-12-24 17 49 07" src="https://github.com/user-attachments/assets/f96aad8c-8d48-4fd4-b054-d7d0d66eea94"; /> ### Was this patch authored or co-authored using generative AI tooling? No -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
