You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/02/07 13:48:46 UTC

[jira] [Commented] (SPARK-23353) Allow ExecutorMetricsUpdate events to be logged to the event log with sampling

    [ https://issues.apache.org/jira/browse/SPARK-23353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16355454#comment-16355454 ] 

Apache Spark commented on SPARK-23353:
--------------------------------------

User 'LantaoJin' has created a pull request for this issue:
https://github.com/apache/spark/pull/20532

> Allow ExecutorMetricsUpdate events to be logged to the event log with sampling
> ------------------------------------------------------------------------------
>
>                 Key: SPARK-23353
>                 URL: https://issues.apache.org/jira/browse/SPARK-23353
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 2.2.1
>            Reporter: Lantao Jin
>            Priority: Minor
>
> [SPARK-22050|https://issues.apache.org/jira/browse/SPARK-22050] give a way to log BlockUpdated events. Actually, the ExecutorMetricsUpdates are also very useful if it can be persisted for further analysis. 
> As a performance reason and actual use case, the PR offers a fraction configuration which can sample the events to be persisted. we also refactor for BlockUpdated with the same sampling way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org