[jira] [Updated] (SPARK-7386) Spark application level metrics application.$AppName.$number.cores doesn't reset on Standalone Master deployment

["Sean Owen (JIRA)" <ji...@apache.org>]

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

Sean Owen updated SPARK-7386:
-----------------------------
    Component/s: Spark Core
       Priority: Minor  (was: Major)

Please set component.
I'm not familiar with this bit, but I recall a similar conversation about a cores metric where some metrics were intended to reflect the amount requested while the job was running. Is that the intent of this one?

> Spark application level metrics application.$AppName.$number.cores doesn't reset on Standalone Master deployment
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-7386
>                 URL: https://issues.apache.org/jira/browse/SPARK-7386
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.3.0
>            Reporter: Bharat Venkat
>            Priority: Minor
>
> Spark publishes a metric called application.$AppName.$number.cores that gets published which monitors number of cores assigned to an application.  However there is a bug as of 1.3 standalone deployment, where this metric doesn't go down to 0 after the application ends.
> It looks like standalone master holds onto the old state and continues to publish a stale metric.



--
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