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/21 00:36:47 UTC
[jira] [Created] (MAPREDUCE-2606) IsolationRunner broken
IsolationRunner broken
----------------------
Key: MAPREDUCE-2606
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2606
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Alejandro Abdelnur
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
[jira] [Commented] (MAPREDUCE-2606) Remove IsolationRunner
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063634#comment-13063634 ]
Hudson commented on MAPREDUCE-2606:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #739 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/739/])
MAPREDUCE-2606. Remove IsolationRunner. Contributed by Alejandro Abdelnur
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1145413
Files :
* /hadoop/common/trunk/mapreduce/src/test/mapred/org/apache/hadoop/mapred/TestIsolationRunner.java
* /hadoop/common/trunk/mapreduce/CHANGES.txt
* /hadoop/common/trunk/mapreduce/src/java/org/apache/hadoop/mapred/MapTask.java
* /hadoop/common/trunk/mapreduce/src/test/mapred/org/apache/hadoop/mapred/TestMapProgress.java
* /hadoop/common/trunk/mapreduce/src/java/org/apache/hadoop/mapred/Task.java
* /hadoop/common/trunk/mapreduce/src/java/org/apache/hadoop/mapred/IsolationRunner.java
* /hadoop/common/trunk/mapreduce/src/docs/src/documentation/content/xdocs/mapred_tutorial.xml
* /hadoop/common/trunk/mapreduce/src/docs/src/documentation/content/xdocs/site.xml
> Remove IsolationRunner
> ----------------------
>
> 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
> Fix For: 0.23.0
>
> 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
[jira] [Updated] (MAPREDUCE-2606) Remove IsolationRunner
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated MAPREDUCE-2606:
-----------------------------------
Release Note: IsolationRunner is no longer maintained. See MAPREDUCE-2637 for its replacement. (was: IsolationRunner is no longer maintained. See MAPREDUCE-2637 for it's replacement. )
> Remove IsolationRunner
> ----------------------
>
> 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
> Fix For: 0.23.0
>
> 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
[jira] [Updated] (MAPREDUCE-2606) Remove IsolationRunner
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated MAPREDUCE-2606:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I've committed this. Thanks Alejandro.
> Remove IsolationRunner
> ----------------------
>
> 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
> Fix For: 0.23.0
>
> 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
[jira] [Commented] (MAPREDUCE-2606) Remove IsolationRunner
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063640#comment-13063640 ]
Todd Lipcon commented on MAPREDUCE-2606:
----------------------------------------
Please add a Release Note entry to this JIRA explaining that it was unmaintained, and pointing to the new JIRA filed for its replacement?
> Remove IsolationRunner
> ----------------------
>
> 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
> Fix For: 0.23.0
>
> 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
[jira] [Updated] (MAPREDUCE-2606) Remove IsolationRunner
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated MAPREDUCE-2606:
-----------------------------------
Fix Version/s: 0.23.0
Hadoop Flags: [Incompatible change, Reviewed]
Summary: Remove IsolationRunner (was: IsolationRunner broken)
> Remove IsolationRunner
> ----------------------
>
> 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
> Fix For: 0.23.0
>
> 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
[jira] [Commented] (MAPREDUCE-2606) IsolationRunner broken
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052986#comment-13052986 ]
Hadoop QA commented on MAPREDUCE-2606:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12483369/MAPREDUCE-2606.patch
against trunk revision 1137017.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause tar ant target to fail.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these core unit tests:
org.apache.hadoop.cli.TestMRCLI
org.apache.hadoop.fs.TestFileSystem
-1 contrib tests. The patch failed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/409//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/409//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/409//console
This message is automatically generated.
> 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
[jira] [Commented] (MAPREDUCE-2606) Remove IsolationRunner
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063930#comment-13063930 ]
Hudson commented on MAPREDUCE-2606:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #735 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/735/])
MAPREDUCE-2606. Remove IsolationRunner. Contributed by Alejandro Abdelnur
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1145413
Files :
* /hadoop/common/trunk/mapreduce/src/test/mapred/org/apache/hadoop/mapred/TestIsolationRunner.java
* /hadoop/common/trunk/mapreduce/CHANGES.txt
* /hadoop/common/trunk/mapreduce/src/java/org/apache/hadoop/mapred/MapTask.java
* /hadoop/common/trunk/mapreduce/src/test/mapred/org/apache/hadoop/mapred/TestMapProgress.java
* /hadoop/common/trunk/mapreduce/src/java/org/apache/hadoop/mapred/Task.java
* /hadoop/common/trunk/mapreduce/src/java/org/apache/hadoop/mapred/IsolationRunner.java
* /hadoop/common/trunk/mapreduce/src/docs/src/documentation/content/xdocs/mapred_tutorial.xml
* /hadoop/common/trunk/mapreduce/src/docs/src/documentation/content/xdocs/site.xml
> Remove IsolationRunner
> ----------------------
>
> 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
> Fix For: 0.23.0
>
> 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
[jira] [Commented] (MAPREDUCE-2606) IsolationRunner broken
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053034#comment-13053034 ]
Alejandro Abdelnur commented on MAPREDUCE-2606:
-----------------------------------------------
I've reverted the patch in my devel environment, run those tests against the trunk and they still fail. Could it be that they are broken?
> 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
[jira] [Updated] (MAPREDUCE-2606) IsolationRunner broken
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (MAPREDUCE-2606) IsolationRunner broken
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated MAPREDUCE-2606:
------------------------------------------
Attachment: MAPREDUCE-2606.patch
Removing IsolationRunner
> IsolationRunner broken
> ----------------------
>
> Key: MAPREDUCE-2606
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2606
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: 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
[jira] [Updated] (MAPREDUCE-2606) Remove IsolationRunner
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins updated MAPREDUCE-2606:
-----------------------------------
Release Note: IsolationRunner is no longer maintained. See MAPREDUCE-2637 for it's replacement.
Done.
> Remove IsolationRunner
> ----------------------
>
> 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
> Fix For: 0.23.0
>
> 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
[jira] [Commented] (MAPREDUCE-2606) IsolationRunner broken
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061616#comment-13061616 ]
Eli Collins commented on MAPREDUCE-2606:
----------------------------------------
Yea, looks like IsolationRunner has bit rot for a long time. Given no one uses it and we have MAPREDUCE-2637 for an MR2 replacement I think we can remove it.
+1
> 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