[
https://issues.apache.org/jira/browse/YARN-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated YARN-10018:
--------------------------------
Description:
There are some places in the container-executor native, where the {{fork()}}
call is not handled properly. This operation can fail with -1, but sometimes
the necessary if branch is missing to validate that it's been successful.
Also, at one location, the return value is defined as an {{int}}, not
{{pid_t}}. It's better to handle this transparently and change it.
was:
There are some places in the container-executor native, where the {{fork()}}
call is not handled properly. This operation can fail with -1, but sometimes
the necessary if branch is missing to validate the success.
Also, at one location, the return value is defined as an {{int}}, not
{{pid_t}}. It's better to handle this transparently and change it.
> container-executor: possible -1 return value of fork() is not always checked
> ----------------------------------------------------------------------------
>
> Key: YARN-10018
> URL: https://issues.apache.org/jira/browse/YARN-10018
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
>
> There are some places in the container-executor native, where the {{fork()}}
> call is not handled properly. This operation can fail with -1, but sometimes
> the necessary if branch is missing to validate that it's been successful.
> Also, at one location, the return value is defined as an {{int}}, not
> {{pid_t}}. It's better to handle this transparently and change it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
