hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack@archive.org (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-41) JAVA_OPTS for the TaskRunner Child
Date Thu, 23 Feb 2006 23:23:37 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-41?page=all ]

stack@archive.org updated HADOOP-41:

    Attachment: TaskRunner_child_javaopts-v2.patch

Second attempt.  Addresses Doug comment.  In this patch, if mapred.child.heap.size is present
in configuration, rather than just ignore it, its heap size setting wins out over any setting
present in mapred.child.java.opts and a warning is emitted that this setting is deprecated.

> JAVA_OPTS for the TaskRunner Child
> ----------------------------------
>          Key: HADOOP-41
>          URL: http://issues.apache.org/jira/browse/HADOOP-41
>      Project: Hadoop
>         Type: Improvement
>   Components: conf
>     Reporter: stack@archive.org
>     Priority: Minor
>  Attachments: TaskRunner_child_javaopts-v2.patch, TaskRunner_child_javaopts.patch
> Currently, its possible to set the java heap size the TaskRunner child runs in, but thats
all thats configurable about the child process.  Hereabouts, we've found it useful being able
to specify other options for the child JVM, especially when debugging and monitoring long-lived
> Examples of why its useful being able to set options are the child include:
> + Being able to set '-server' option or '-c64'.
> + Passing logging.properties to configure child logging.
> + Enable and capture to file verbose GC logging or start the SUN JVM JMX agent for the
child process.  Allows connecting with jconsole to watch long-lived children, their heap and
thread usage, and when seemingly hung, take thread dumps.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message