hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-217) Tasks to run on a different jvm version than the TaskTracker
Date Sun, 26 Apr 2015 01:40:39 GMT

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

Allen Wittenauer resolved MAPREDUCE-217.
----------------------------------------
    Resolution: Fixed

This is possible to do in YARN.  Closing as fixed.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message