Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-453

Provide more flexibility in the way tasks are run



    • New Feature
    • Status: Resolved
    • Minor
    • Resolution: Duplicate
    • None
    • None
    • None
    • None


      The aim
      With HADOOP-3421 speaking about sharing a cluster among more than one organization (so potentially with non-cooperative users), and posts on the ML speaking about virtualization and the ability to re-use the TaskTracker's VM to run new tasks, it could be useful for admins to choose the way TaskRunners run their children.

      More specifically, it could be useful to provide a way to imprison a Task in its working directory, or in a virtual machine.
      In some cases, reusing the VM might be useful, since it seems that this feature is really wanted (HADOOP-249).

      What I propose is a new class, called called SeperateVMTaskWrapper which contains the current logic for running tasks in another JVM. This class extends another, called TaskWrapper, which could be inherited to provide new ways of running tasks.
      As part of this issue I would also like to provide two other TaskWrappers : the first would run the tasks as Thread of the TaskRunner's VM (if it is possible without too much changes), the second would use a fixed pool of local unix accounts to insulate tasks from each others (so potentially non-cooperating users will be hable to share a cluster, as described in HADOOP-3421).


        1. userBasedInsulator.sh
          2 kB
          Brice Arnould
        2. TaskWrapper_v0.patch
          25 kB
          Brice Arnould

        Issue Links



              un_brice Brice Arnould
              un_brice Brice Arnould
              0 Vote for this issue
              16 Start watching this issue