hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-217) Tasks to run on a different jvm version than the TaskTracker
Date Fri, 23 Oct 2009 10:59:59 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amar Kamat updated MAPREDUCE-217:
---------------------------------

    Attachment: mapreduce-217-v1.0.patch

Attaching a patch that 
# allows the child jvm to be configured via mapreduce.task.jvm
# gives preference to child classpath over tasktracker (parent) classpath entries

Result of test-patch
[exec] +1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     +1 tests included.  The patch appears to include 3 new or modified tests.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
warnings.
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec] 
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.

Testing the patch. Mainly I will test some 64bit jvm apps which includes 64 bit libs etc.

The testcase requires the system-property mapreduce.task.jvm to be set to an alternate jvm.

> Tasks to run on a different jvm version than the TaskTracker
> ------------------------------------------------------------
>
>                 Key: MAPREDUCE-217
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-217
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>         Environment: linux
>            Reporter: Koji Noguchi
>            Assignee: Amar Kamat
>         Attachments: mapreduce-217-v1.0.patch
>
>
> We use 32-bit jvm for TaskTrackers. 
> Sometimes our users want to call 64-bit JNI libraries from their tasks.
> This requires tasks to be running on 64-bit jvm.
> On Solaris, you can simply use -d32/-d64 to choose, but on Linux, it's on a completely
different package.
> So far, tasks run on the same jvm version as the TaskTracker.
> {noformat}
> // use same jvm as parent
> File jvm =   new File(new File(System.getProperty("java.home"), "bin"), "java");
> {noformat}
> Is it possible to let users provide a java home path 
> or let them choose from a pre-selected list of paths?

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