You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@systemml.apache.org by "Felix Schüler (JIRA)" <ji...@apache.org> on 2016/11/23 23:51:59 UTC
[jira] [Commented] (SYSTEMML-1126) Custom Configuration parameters
are lost in remote execution
[ https://issues.apache.org/jira/browse/SYSTEMML-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691697#comment-15691697 ]
Felix Schüler commented on SYSTEMML-1126:
-----------------------------------------
As far as I can see the problem is that the static variables in the ConfigurationManager are serialized and deserialized in different JVMs, leading to the use of defaults in the remote JVMs.
> Custom Configuration parameters are lost in remote execution
> ------------------------------------------------------------
>
> Key: SYSTEMML-1126
> URL: https://issues.apache.org/jira/browse/SYSTEMML-1126
> Project: SystemML
> Issue Type: Bug
> Components: Runtime
> Reporter: Felix Schüler
>
> When running a remote job, a custom configuration that was set with the -config parameter is not available to the workers.
> The problem is that the Configuration manager is initialized as a static Singleton on the driver and holds a threadlocal configuration that was initialized for the driver process but not on the remote workers. Therefore, they will always use the defaults.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)