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 Tue, 28 Apr 2009 06:19:30 GMT

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

Amar Kamat commented on HADOOP-5643:
------------------------------------

Had an offline discussion with Devaraj and we think it makes sense to provide a default location
for mapred.hosts.exclude. The purpose of doing this is to provide persistence. The default
file would be something like ${hadoop.log.dir}/history/hosts.exclude. By default the jobtracker
persists the decommission/recommission host info in this file.

@Eric
I think we should do what we do for job killing i.e private actions thingy. There is always
the option to do it either via {{refresh}} or {{-decommission/-recommission}} command line
option. All the admin operations at the jobtracker will be checked for owner access. For now
I think only the user who runs the jobtracker should be allowed to fire these commands. Thoughts?

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


Mime
View raw message