hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5643) Ability to blacklist tasktracker
Date Fri, 24 Apr 2009 11:12:30 GMT

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

Amar Kamat commented on HADOOP-5643:

One more thing i forgot to add is that the jobtracker already reads the hosts file and the
exclude file but just once. There is no refresh facility to it. I think we can add that to
MR too. So here is the sequence of things :
# files to include can be specified via mapred.hosts and will be read by the jobtracker upon
# files to exclude can be specified via mapred.hosts.exclude and will also be read by the
jobtracker upon init
# Admins can change these files and invoke a _refresh_ from the command line (maybe from the
webui too). These files will be loaded back.
# If the hosts are added via command line or webui, it will be appended to the include/exclude
files. So that upon next restart, the previously included/excluded host info is re-used.

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

View raw message