hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajiv Chittajallu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5643) Ability to blacklist tasktracker
Date Thu, 30 Apr 2009 16:34:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704691#action_12704691
] 

Rajiv Chittajallu commented on HADOOP-5643:
-------------------------------------------

>While testing the patch, we found that manually changing the excludes file (maintained
by the jobtracker) results in checksum error.

For the name NameNode, this is allowed. JT should do the same. 




> Ability to blacklist tasktracker
> --------------------------------
>
>                 Key: HADOOP-5643
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5643
>             Project: Hadoop Core
>          Issue Type: New Feature
>    Affects Versions: 0.20.0
>            Reporter: Rajiv Chittajallu
>            Assignee: Amar Kamat
>         Attachments: HADOOP-5643-v3.4.patch, HADOOP-5643-v4.0.patch
>
>
> Its not always possible to shutdown the tasktracker to stop scheduling tasks on the node.
(eg you can't login to the node but the TT is up). 
> This can be via 
>   * mapred.exclude and should be refreshed with out restarting the tasktracker
>   * hadoop job -fail-tracker <tracker id>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message