hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Gummadi (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HADOOP-5614) SIGKILL should be sent only after a while after SIGTERM is sent in sigkillInCurrentThread() similar to what sigKillThread is doing
Date Mon, 06 Apr 2009 07:24:13 GMT

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

Ravi Gummadi reassigned HADOOP-5614:
------------------------------------

    Assignee: Ravi Gummadi

> SIGKILL should be sent only after a while after SIGTERM is sent in sigkillInCurrentThread()
similar to what sigKillThread is doing
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5614
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5614
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>
> sigkillInCurrentThread() doesn't give time for graceful exit of taskJvm after SIGTERM
is sent. Currently mapred.tasktracker.tasks.sleeptime-before-sigkill is used by SigKillThread
only. It should be used by sigKillInCurrentThread() also.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message