[
https://issues.apache.org/jira/browse/SYSTEMML-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883908#comment-15883908
]
Matthias Boehm commented on SYSTEMML-1126:
------------------------------------------
Quick update: I was able to reproduce this behavior. This issue has been
introduced with SYSTEMML-584 and it affects, in the context of parfor spark
execute jobs, all configurations that are taken over from the dml config into
our compiler config (i.e., optimization level and blocksize).
> 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
> Assignee: 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.15#6346)
