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

Posted to issues@spark.apache.org by "Saisai Shao (JIRA)" <ji...@apache.org> on 2017/09/28 06:53:00 UTC

[jira] [Resolved] (SPARK-22135) metrics in spark-dispatcher not being registered properly

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

Saisai Shao resolved SPARK-22135.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0
                   2.2.1

Issue resolved by pull request 19358
[https://github.com/apache/spark/pull/19358]

> metrics in spark-dispatcher not being registered properly
> ---------------------------------------------------------
>
>                 Key: SPARK-22135
>                 URL: https://issues.apache.org/jira/browse/SPARK-22135
>             Project: Spark
>          Issue Type: Bug
>          Components: Deploy, Mesos
>    Affects Versions: 2.1.0, 2.2.0
>            Reporter: paul mackles
>            Priority: Minor
>             Fix For: 2.2.1, 2.3.0
>
>
> There is a bug in the way that the metrics in org.apache.spark.scheduler.cluster.mesos.MesosClusterSchedulerSource are initialized such that they are never registered with the underlying registry. Basically, each call to the overridden "metricRegistry" function results in the creation of a new registry. PR is forthcoming.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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