[
https://issues.apache.org/jira/browse/SPARK-32119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147750#comment-17147750
]
Luca Canali edited comment on SPARK-32119 at 6/29/20, 8:09 PM:
---------------------------------------------------------------
I am adding the comment that the limitation discussed in this JIRA was known at
implementation time and is documented at:
https://spark.apache.org/docs/latest/monitoring.html#advanced-instrumentation
In short, in Spark 3.0.0, one can use `--jars` to distribute a jar with Plugin
code only with YARN, for all the other cluster managers see the workarounds
proposed in the documentation.
was (Author: lucacanali):
I am adding the comment that the limitation discussed in this JIRA was known at
implementation time and is documented at:
https://spark.apache.org/docs/latest/monitoring.html#advanced-instrumentation
In short, in Spark 3.0.0, one can use --jars to send Plugin code that the
exectutors only with YARN, for all the other cluster managers see the
workarounds proposed in the documentation.
> ExecutorPlugin doesn't work with Standalone Cluster
> ---------------------------------------------------
>
> Key: SPARK-32119
> URL: https://issues.apache.org/jira/browse/SPARK-32119
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 3.0.1, 3.1.0
> Reporter: Kousuke Saruta
> Assignee: Kousuke Saruta
> Priority: Major
>
> ExecutorPlugin can't work with Standalone Cluster (maybe with other cluster
> manager too except YARN. )
> when a jar which contains plugins and files used by the plugins are added by
> --jars and --files option with spark-submit.
> This is because jars and files added by --jars and --files are not loaded on
> Executor initialization.
> I confirmed it works with YARN because jars/files are distributed as
> distributed cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
