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 Thu, 30 Apr 2009 11:00:31 GMT

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

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

While testing the patch, we found that manually changing the excludes file (maintained by
the jobtracker) results in checksum error. So, for now we think keeping it as it is (i.e using
java to write/read) makes more sense. Also here are some of the test bugs :
# documentation for command line is not sufficient
# passing a wrong file to hosts reader causes the earlier data to be lost. So the correct
way would be to first load the new file and on success replace the internal structures. 
# web ui doesnt work as expected. 

Will upload a new patch soon.

> 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