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] Updated: (HADOOP-4374) JVM should not be killed but given an opportunity to exit gracefully
Date Wed, 25 Mar 2009 14:58:53 GMT

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

Ravi Gummadi updated HADOOP-4374:

    Attachment: HADOOP-4374.patch

Attaching patch that has the following:

(1) Added a shutdownHook that does syncLogs sothat logs of the current task are flushed and
log.index is up to date in cases like System.exit(), or killed using signals(other than SIGKILL).
(2) Changed WriteToIndexFile() to write to a temporary index file first and then rename to
log.index sothat updates to log.index file are atomic.

Please review and provide your comments.

> JVM should not be killed but given an opportunity to exit gracefully
> --------------------------------------------------------------------
>                 Key: HADOOP-4374
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4374
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Devaraj Das
>            Assignee: Ravi Gummadi
>             Fix For: 0.20.0
>         Attachments: HADOOP-4374.patch
> When the tasktracker picks an idle JVM for purging, it should signal the JVM to exit
gracefully, rather than forcefully killing it. This might have the unfortunate side effect
of logs not fully flushed yet in some cases.

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

View raw message