[
https://issues.apache.org/jira/browse/SPARK-22135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
paul mackles updated SPARK-22135:
---------------------------------
Description: 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. (was: 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. Patch is forthcoming.)
> 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
>
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
