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 "eric baldeschwieler (JIRA)" <ji...@apache.org> on 2009/05/01 06:53:31 UTC

[jira] Commented: (HADOOP-5643) Ability to blacklist tasktracker

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

eric baldeschwieler commented on HADOOP-5643:
---------------------------------------------

I think we are going through an expensive process of reinventing the wheel here.  We should think about solving this sort of issue once by maintain such lists in a plugable source of configuration and supporting the ability to "hup" the service.  

We should then implement config in LDAP / SQL / or some other service via plugins and then we can modify these configurations in an environment with lots of tools to support this stuff.  Adding ad hock commands and odd side files that will be lost if we need to swap hardware is awkward.

> 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.