hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2637) Providing options to debug the mapreduce user code (Mapper, Reducer, Combiner, Sort implementations)
Date Fri, 18 May 2012 20:21:10 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279151#comment-13279151
] 

Harsh J commented on MAPREDUCE-2637:
------------------------------------

Shouldn't we raise issues on MRUNIT to tackle all debug-ability issues? I believe thats where
it ought to go.

For developers of YARN framework who wish to debug at the container levels, the way is to
do it via the IDE. We can repurpose this JIRA to have that documented.
                
> Providing options to debug the mapreduce user code (Mapper, Reducer, Combiner, Sort implementations)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2637
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2637
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: tasktracker
>            Reporter: Devaraj K
>            Assignee: Devaraj K
>
> Presently Hadoop provides "mapred.child.java.opts" configuration which can be used to
set JVM options for Child JVM running Map or Reduce Task. 
> If we need to remote debug the Child JVM, we can add remote debugging options to this
configuration value.
> But this will work only for single Child JVM. Other children will fail as the remote
debugging port is already used.
> We cannot specify the remote debugging port dynamically.
> As a result, it's not possible to remote debug multiple Child JVMs.
> As a solution to this problem, we can provide a configuration to debug Task JVMs in this
scenario.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message