You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kousuke Saruta (JIRA)" <ji...@apache.org> on 2014/09/05 16:44:28 UTC
[jira] [Updated] (SPARK-3377) Don't mix metrics from different
applications otherwise we cannot distinguish
[ https://issues.apache.org/jira/browse/SPARK-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kousuke Saruta updated SPARK-3377:
----------------------------------
Summary: Don't mix metrics from different applications otherwise we cannot distinguish (was: Don't mix metrics from different applications)
> Don't mix metrics from different applications otherwise we cannot distinguish
> -----------------------------------------------------------------------------
>
> Key: SPARK-3377
> URL: https://issues.apache.org/jira/browse/SPARK-3377
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.1.0
> Reporter: Kousuke Saruta
> Priority: Critical
>
> I'm using codahale base MetricsSystem of Spark with JMX or Graphite, and I saw following 2 problems.
> (1) When applications which have same spark.app.name run on cluster at the same time, some metrics names jumble up together. e.g, SparkPi.DAGScheduler.stage.failedStages jumble.
> (2) When 2+ executors run on the same machine, JVM metrics of each executors jumble. e.g, We current implementation cannot distinguish metric "jvm.memory" is for which executor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org