You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Mridul Muralidharan (Jira)" <ji...@apache.org> on 2025/09/01 04:58:00 UTC
[jira] [Assigned] (SPARK-53156) Better Capture Driver Memory Metrics when the app proactively terminates due to resource issues
[ https://issues.apache.org/jira/browse/SPARK-53156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mridul Muralidharan reassigned SPARK-53156:
-------------------------------------------
Assignee: Victor Sunderland
> Better Capture Driver Memory Metrics when the app proactively terminates due to resource issues
> -----------------------------------------------------------------------------------------------
>
> Key: SPARK-53156
> URL: https://issues.apache.org/jira/browse/SPARK-53156
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 4.1.0
> Reporter: Victor Sunderland
> Assignee: Victor Sunderland
> Priority: Minor
> Labels: pull-request-available
>
> When the application proactively terminates due to some memory issues at the driver (SparkOOM, result size too large, etc...), due to metric sampling issues we will often miss this resourcing problem in the memory metrics and in the event log. We will abort the job before we capture accurate metrics for the driver. We should improve this case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org