spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-5770) Use addJar() to upload a new jar file to executor, it can't be added to classloader
Date Thu, 12 Feb 2015 11:47:11 GMT

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

Sean Owen commented on SPARK-5770:
----------------------------------

Can you be more specific about where you think the code path doesn't copy the new file? your
PR does not touch the copying code but disables overwrite entirely, which is not OK.

> Use addJar() to upload a new jar file to executor, it can't be added to classloader
> -----------------------------------------------------------------------------------
>
>                 Key: SPARK-5770
>                 URL: https://issues.apache.org/jira/browse/SPARK-5770
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>            Reporter: meiyoula
>
> First use addJar() to upload a jar to the executor, then change the jar content and upload
it again. We can see the jar file in the local has be updated, but the classloader still load
the old one. The executor log has no error or exception to point it.
> I use spark-shell to test it. And set "spark.files.overwrite" is true.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message