Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1891932134.1238048633190.JavaMail.jira@brutus>
Date: Wed, 25 Mar 2009 23:23:53 -0700 (PDT)
From: "Ravi Gummadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4374) JVM should not be killed but given an
 opportunity to exit gracefully
In-Reply-To: <1486054586.1223468504316.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ravi Gummadi updated HADOOP-4374:
---------------------------------

    Release Note: 
This patch (1) Adds 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) Changes writeToIndexFile() to write to a temporary index file first and then rename to log.index sothat updates to log.index file are atomic.
          Status: Patch Available  (was: Open)

Marking this as Patch Available sothat hudson will run tests.

> 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, HADOOP-4374.v1.1.patch, HADOOP-4374.v1.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.