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

2018-02-07 Thread Apache Spark (JIRA)

 [ 
https://issues.apache.org/jira/browse/SPARK-23353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apache Spark reassigned SPARK-23353:


Assignee: (was: Apache Spark)

> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



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

2018-02-07 Thread Apache Spark (JIRA)

 [ 
https://issues.apache.org/jira/browse/SPARK-23353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apache Spark reassigned SPARK-23353:


Assignee: Apache Spark

> 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
>Assignee: Apache Spark
>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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org