You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Imran Rashid (Jira)" <ji...@apache.org> on 2020/01/31 20:31:00 UTC
[jira] [Resolved] (SPARK-27324) document configurations related to
executor metrics
[ https://issues.apache.org/jira/browse/SPARK-27324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Imran Rashid resolved SPARK-27324.
----------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
> document configurations related to executor metrics
> ---------------------------------------------------
>
> Key: SPARK-27324
> URL: https://issues.apache.org/jira/browse/SPARK-27324
> Project: Spark
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 3.0.0
> Reporter: Wing Yew Poon
> Assignee: Wing Yew Poon
> Priority: Major
> Fix For: 3.0.0
>
>
> SPARK-23429 introduced executor memory metrics, and the configuration, spark.eventLog.logStageExecutorMetrics.enabled, that determines if per-stage per-executor metric peaks get written to the event log. (The metrics are polled and sent in the heartbeat, and this is always done; the configuration is only to determine if aggregated metric peaks are written to the event log.)
> SPARK-24958 added proc fs based metrics to the executor memory metrics, and the configuration, spark.eventLog.logStageExecutorProcessTreeMetrics.enabled, to determine if these additional (more expensive) metrics are collected when metrics are polled.
> SPARK-26329 will introduce a configuration, spark.executor.metrics.pollingInterval, to allow polling at more frequent intervals than the executor heartbeat.
> These configurations and how they relate to each other should be documented in the Configuration page.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org