You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kousuke Saruta (Jira)" <ji...@apache.org> on 2020/09/01 20:39:00 UTC

[jira] [Commented] (SPARK-32119) ExecutorPlugin doesn't work with Standalone Cluster and Kubernetes with --jars

    [ https://issues.apache.org/jira/browse/SPARK-32119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188808#comment-17188808 ] 

Kousuke Saruta commented on SPARK-32119:
----------------------------------------

Yeah, it's a bug fix so we may have a chance to backport this fix to 3.0.1.
I'll make a backport PR.

> ExecutorPlugin doesn't work with Standalone Cluster and Kubernetes with --jars
> ------------------------------------------------------------------------------
>
>                 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
>             Fix For: 3.1.0
>
>
> ExecutorPlugin can't work with Standalone Cluster and Kubernetes
>  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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org