You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "stack@archive.org (JIRA)" <ji...@apache.org> on 2006/02/18 01:48:24 UTC
[jira] Created: (HADOOP-41) JAVA_OPTS for the TaskRunner Child
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
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 processes.
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-41) JAVA_OPTS for the TaskRunner Child
Posted by "stack@archive.org (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-41?page=all ]
stack@archive.org updated HADOOP-41:
------------------------------------
Attachment: TaskRunner_child_javaopts.patch
Attached is a suggested patch for TaskRunner that reads a new configuration option, mapred.child.java.opts. This new configuration subsumes mapred.child.heap.size. Paul Baclace coauthored this patch.
> 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.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 processes.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (HADOOP-41) JAVA_OPTS for the TaskRunner Child
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-41?page=all ]
Doug Cutting resolved HADOOP-41:
--------------------------------
Fix Version: 0.1
Resolution: Fixed
I just committed this. Thanks, Michael!
> 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
> Fix For: 0.1
> 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 processes.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-41) JAVA_OPTS for the TaskRunner Child
Posted by "stack@archive.org (JIRA)" <ji...@apache.org>.
[ 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 processes.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-41) JAVA_OPTS for the TaskRunner Child
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-41?page=comments#action_12367435 ]
Doug Cutting commented on HADOOP-41:
------------------------------------
I like this, except that it is not back-compatible. We should continue to support mapred.child.heap.size, so that folks who upgrade are not broken.
> 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.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 processes.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira