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

Sean Owen resolved SPARK-4544.
------------------------------
    Resolution: Duplicate

I'd like to bundle this under SPARK-5847, which proposes more general control 
over the namespacing, which could include "instance" as a higher-level grouping 
than the current app ID.

> Spark JVM Metrics doesn't have context.
> ---------------------------------------
>
>                 Key: SPARK-4544
>                 URL: https://issues.apache.org/jira/browse/SPARK-4544
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.1.0
>            Reporter: Sreepathi Prasanna
>
> If we enable jvm metrics for executor, master, worker, driver instances, we 
> don't have context where they are coming from ?
> This can be a issue if we are collecting all the metrics from different 
> instances are storing into common datastore. 
> This is mainly running Spark on Yarn but i believe Spark standalone has also 
> this problems.
> It would be good if we attach some context for jvm metrics. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to