[jira] [Updated] (SAMZA-805) "task.opts" config is not passed in case of ProcessJobFactory

["Boris Shkolnik (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SAMZA-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boris Shkolnik updated SAMZA-805:
---------------------------------
    Description: 
 
ProcessJobFactory is creating a separate process by using ProcessBuilder. ProcessBuilder pulls its settings from the environment.
So if the user specifies task.opts and java.home in the configs they need to be passed to the ProcessBuilder environment. 
But currently we strip the configs of all the values, except the ones required by JobCoordinator.

As the result the process is created without task.opts option. This causes issues with heap memory size settings, debugging and so on.

The fix is to pass full config to the ProcessBuilder in case of ProcessJob.

  was:
 
ProcessJobFactory is creating a separate process by using ProcessBuilder. ProcessBuilder pulls its settings from the environment.
So if the user specifies task.opts and java.home in the configs they need to be passed to the ProcessBuilder environment. 
But currently we strip the configs of all the values, except the ones required by JobCoordinator.

As the result the process is created without task.opts option. This causes issues with heap memory size settings, debugging and so on.

The fix is to pass task.opts and java.home to the ProcessBuilder in case of ProcessJobFactory class.factory.


> "task.opts" config  is not passed in case of ProcessJobFactory
> --------------------------------------------------------------
>
>                 Key: SAMZA-805
>                 URL: https://issues.apache.org/jira/browse/SAMZA-805
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.10.0
>            Reporter: Boris Shkolnik
>            Assignee: Boris Shkolnik
>
>  
> ProcessJobFactory is creating a separate process by using ProcessBuilder. ProcessBuilder pulls its settings from the environment.
> So if the user specifies task.opts and java.home in the configs they need to be passed to the ProcessBuilder environment. 
> But currently we strip the configs of all the values, except the ones required by JobCoordinator.
> As the result the process is created without task.opts option. This causes issues with heap memory size settings, debugging and so on.
> The fix is to pass full config to the ProcessBuilder in case of ProcessJob.



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