[
https://issues.apache.org/jira/browse/HADOOP-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693991#action_12693991
]
Amareshwari Sriramadasu commented on HADOOP-4374:
-------------------------------------------------
bq. why log the exception with stringifyException instead of
log.error("Exception " + e, e) ?
I don't know much about log.error functionality. If it also retains stacktrace,
using any of stringifyException or log.error("Exception " + e,e) is fine with
me.
bq. I know a lot of the code uses stringifyException(), but thought the
codebase was moving away from it?
If this is expected, I think it is time to deprecated stringifyException().
> 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.
