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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2006/09/26 07:32:50 UTC
[jira] Created: (HADOOP-560) tasks should have a "killed" state
tasks should have a "killed" state
----------------------------------
Key: HADOOP-560
URL: http://issues.apache.org/jira/browse/HADOOP-560
Project: Hadoop
Issue Type: Improvement
Components: mapred
Affects Versions: 0.6.2
Reporter: Owen O'Malley
Assigned To: Owen O'Malley
Fix For: 0.7.0
Tasks should have a state that reflects the fact that they were killed instead of failed to help the user understand what happened to the task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-560) tasks should have a "killed" state
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-560?page=all ]
Owen O'Malley updated HADOOP-560:
---------------------------------
Attachment: kill-state.patch
This patch:
1. Introduces an enum for the Task state, called TaskStatus.State.
2. The enum values match the old integer constants by name and value.
3. The TaskStatus' serialization is kept the same.
4. A bug based on confusion between the Job State and Task State values is fixed (go type-safe enums!)
5. A new killed state is added for Tasks.
6. The web/ui for jobs shows the count for tasks that have been killed.
7. The code for converting the Task Status State to string in the web/ui has been removed.
> tasks should have a "killed" state
> ----------------------------------
>
> Key: HADOOP-560
> URL: http://issues.apache.org/jira/browse/HADOOP-560
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.6.2
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.7.0
>
> Attachments: kill-state.patch
>
>
> Tasks should have a state that reflects the fact that they were killed instead of failed to help the user understand what happened to the task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-560) tasks should have a "killed" state
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-560?page=all ]
Owen O'Malley updated HADOOP-560:
---------------------------------
Status: Patch Available (was: Open)
> tasks should have a "killed" state
> ----------------------------------
>
> Key: HADOOP-560
> URL: http://issues.apache.org/jira/browse/HADOOP-560
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.6.2
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.7.0
>
> Attachments: kill-state-2.patch, kill-state.patch
>
>
> Tasks should have a state that reflects the fact that they were killed instead of failed to help the user understand what happened to the task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-560) tasks should have a "killed" state
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-560?page=all ]
Doug Cutting updated HADOOP-560:
--------------------------------
Status: Resolved (was: Patch Available)
Resolution: Fixed
I just committed this. Thanks, Owen!
> tasks should have a "killed" state
> ----------------------------------
>
> Key: HADOOP-560
> URL: http://issues.apache.org/jira/browse/HADOOP-560
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.6.2
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.7.0
>
> Attachments: kill-state-2.patch, kill-state.patch
>
>
> Tasks should have a state that reflects the fact that they were killed instead of failed to help the user understand what happened to the task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-560) tasks should have a "killed" state
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-560?page=all ]
Owen O'Malley updated HADOOP-560:
---------------------------------
Attachment: kill-state-2.patch
I fixed another couple of things:
1. my previous patch tickled a previous bug that was causing jobs to not complete when their last reduce finished.
2. made the minimr cluster wait until it is out of safe mode
> tasks should have a "killed" state
> ----------------------------------
>
> Key: HADOOP-560
> URL: http://issues.apache.org/jira/browse/HADOOP-560
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.6.2
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.7.0
>
> Attachments: kill-state-2.patch, kill-state.patch
>
>
> Tasks should have a state that reflects the fact that they were killed instead of failed to help the user understand what happened to the task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-560) tasks should have a "killed" state
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-560?page=all ]
Owen O'Malley updated HADOOP-560:
---------------------------------
Status: Patch Available (was: Open)
> tasks should have a "killed" state
> ----------------------------------
>
> Key: HADOOP-560
> URL: http://issues.apache.org/jira/browse/HADOOP-560
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.6.2
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.7.0
>
> Attachments: kill-state.patch
>
>
> Tasks should have a state that reflects the fact that they were killed instead of failed to help the user understand what happened to the task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-560) tasks should have a "killed" state
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-560?page=all ]
Doug Cutting updated HADOOP-560:
--------------------------------
Status: Open (was: Patch Available)
This is causing some of the unit tests to hang.
> tasks should have a "killed" state
> ----------------------------------
>
> Key: HADOOP-560
> URL: http://issues.apache.org/jira/browse/HADOOP-560
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.6.2
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.7.0
>
> Attachments: kill-state.patch
>
>
> Tasks should have a state that reflects the fact that they were killed instead of failed to help the user understand what happened to the task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira