hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3678) DelayedProcessKiller may kill other process other than container
Date Wed, 27 May 2015 12:42:33 GMT

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

Hadoop QA commented on YARN-3678:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply the patch during
dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12735592/YARN-3678.patch |
| Optional Tests |  |
| git revision | trunk / bb18163 |
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/8099/console |


This message was automatically generated.

> DelayedProcessKiller may kill other process other than container
> ----------------------------------------------------------------
>
>                 Key: YARN-3678
>                 URL: https://issues.apache.org/jira/browse/YARN-3678
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.6.0
>            Reporter: gu-chi
>            Priority: Critical
>         Attachments: YARN-3678.patch
>
>
> Suppose one container finished, then it will do clean up, the PID file still exist and
will trigger once singalContainer, this will kill the process with the pid in PID file, but
as container already finished, so this PID may be occupied by other process, this may cause
serious issue.
> As I know, my NM was killed unexpectedly, what I described can be the cause. Even rarely
occur.



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

Mime
View raw message