You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2009/02/17 06:37:59 UTC
[jira] Created: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
------------------------------------------------------------------------------------------------------
Key: HADOOP-5269
URL: https://issues.apache.org/jira/browse/HADOOP-5269
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Affects Versions: 0.19.1
Reporter: Amareshwari Sriramadasu
Assignee: Amareshwari Sriramadasu
Priority: Blocker
Fix For: 0.19.1
Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
-> Task got an exception
-> Sets the phase to CLEANUP
-> The task tries to do cleanup. and it doesn't respond after that.
-> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
-> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-5269:
--------------------------------------------
Fix Version/s: 0.19.2
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.2, 0.20.0, 0.21.0
>
> Attachments: patch-5269-0.19-0.20.txt, patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-5269:
--------------------------------------------
Status: Patch Available (was: Open)
test-patch result :
{noformat}
[exec]
[exec]
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the total number of release audit warnings.
[exec]
{noformat}
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.1, 0.20.0
>
> Attachments: patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-5269:
--------------------------------------------
Attachment: (was: patch-5269-0.19-0.20.txt)
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.1, 0.20.0
>
> Attachments: patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676884#action_12676884 ]
Devaraj Das commented on HADOOP-5269:
-------------------------------------
I committed this to the 0.19 branch.
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.2, 0.20.0, 0.21.0
>
> Attachments: patch-5269-0.19-0.20.txt, patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-5269:
-------------------------------------
Fix Version/s: 0.20.0
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.1, 0.20.0
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-5269:
--------------------------------------------
Attachment: patch-5269-0.19-0.20.txt
Patch for 0.19 and 0.20. Earlier patch had an unnecessary comment... removed that.
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.1, 0.20.0
>
> Attachments: patch-5269-0.19-0.20.txt, patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675278#action_12675278 ]
Amareshwari Sriramadasu commented on HADOOP-5269:
-------------------------------------------------
ant tests passed on my machine.
Ran Reliability test and Sort benchmark.
Also verified OutofMemory run on which Vinod saw this issue.
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.1, 0.20.0
>
> Attachments: patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-5269:
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.19.1)
0.21.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this to the 0.20 branch and trunk. Thanks, Amareshwari! (After 0.19.1 is released for which voting is going on, we should commit this to 0.19 branch as well)
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.20.0, 0.21.0
>
> Attachments: patch-5269-0.19-0.20.txt, patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-5269:
--------------------------------------------
Attachment: patch-5269-0.19-0.20.txt
Patch for 0.19 and 0.20
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.1, 0.20.0
>
> Attachments: patch-5269-0.19-0.20.txt, patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-5269:
--------------------------------------------
Attachment: patch-5269.txt
Attaching patch with the fix.
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.19.1, 0.20.0
>
> Attachments: patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-5269) TaskTracker.runningTasks holding
FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675933#action_12675933 ]
Hudson commented on HADOOP-5269:
--------------------------------
Integrated in Hadoop-trunk #763 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/763/])
> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5269
> URL: https://issues.apache.org/jira/browse/HADOOP-5269
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.1
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.20.0, 0.21.0
>
> Attachments: patch-5269-0.19-0.20.txt, patch-5269.txt
>
>
> Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
> -> Task got an exception
> -> Sets the phase to CLEANUP
> -> The task tries to do cleanup. and it doesn't respond after that.
> -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
> -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).
> I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.