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 Tue, 31 Mar 2009 12:45:52 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.v1.2.patch

Attaching patch removing LOG.warn and LOG.debug from shutdown hook as log manager might already
be shutdown by the time shutdown hook is executed. Also removed syncLogs() call from finally
bock in Child.java as shutdown hook takes care of that.

> 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.2.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.


Mime
View raw message