[
https://issues.apache.org/jira/browse/SPARK-26419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728125#comment-16728125
]
Hyukjin Kwon commented on SPARK-26419:
--------------------------------------
Please avoid to set a Critical+ which is usually reserved for committers.
> spark metric source
> -------------------
>
> Key: SPARK-26419
> URL: https://issues.apache.org/jira/browse/SPARK-26419
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.0.0
> Reporter: Si Chen
> Priority: Major
> Attachments: image-2018-12-20-17-05-42-245.png,
> image-2018-12-20-17-07-40-920.png, image-2018-12-20-17-07-48-020.png,
> image-2018-12-20-17-11-44-568.png, image-2018-12-20-17-14-35-157.png
>
>
> Today I write a metric source to collect HikariCp metrics.
> My source code like this:
> !image-2018-12-20-17-05-42-245.png|width=475,height=184!
> Metrics.properties
> !image-2018-12-20-17-07-48-020.png|width=533,height=121!
> My applicaiton run in yarn-cluster mode.
> Driver normal running. In graphite i can see the hikaricp metrics
> !image-2018-12-20-17-11-44-568.png|width=468,height=118!
> But the executor didn`t collect the hikaricp metric to graphite, So I see the
> executor`s log I found some thing
> !image-2018-12-20-17-14-35-157.png|width=666,height=331!
> So it can`t reflet this class because it can not find this class,But I`m
> sure this class has packaged in the jar.And Drive is OK can find this class.
> Why can`t executor find this class?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
