You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2011/06/22 00:47:47 UTC

[jira] [Updated] (MAPREDUCE-2606) IsolationRunner broken

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

Alejandro Abdelnur updated MAPREDUCE-2606:
------------------------------------------

    Assignee: Alejandro Abdelnur
      Status: Patch Available  (was: Open)

> IsolationRunner broken
> ----------------------
>
>                 Key: MAPREDUCE-2606
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2606
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: MAPREDUCE-2606.patch
>
>
> IsolationRunner it seems it has been broken for a while, it gives a NPE when trying to use it.
> In addition, it supports only Map tasks; to use it the user must ssh to the node where the task failed; and unless the job has been configured to keep local files, the job must be run again.
> Because of this, IMO, the current implementation of IsolationRunner is not of much use.
> Any objection to remove it from trunk and if people have the need for such functionality to open another JIRA to build this functionality supported by the JobTracker (ie via the UI console)?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira