[
https://issues.apache.org/jira/browse/MAPREDUCE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772912#action_12772912
]
Amar Kamat commented on MAPREDUCE-217:
--------------------------------------
Except TestTaskTrackerMemoryManager (timeout), all tests have passed. Manually
testing the patch.
> 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, mapreduce-217-v1.1.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.
