You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sreekanth Ramakrishnan (JIRA)" <ji...@apache.org> on 2009/08/28 06:10:59 UTC
[jira] Updated: (MAPREDUCE-682) Reserved tasktrackers should be
removed when a node is globally blacklisted
[ https://issues.apache.org/jira/browse/MAPREDUCE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sreekanth Ramakrishnan updated MAPREDUCE-682:
---------------------------------------------
Release Note: Fixes the issue with respect to high ram job reservation not being cleared when the task tracker is black listed.
> Reserved tasktrackers should be removed when a node is globally blacklisted
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-682
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-682
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.21.0
> Reporter: Hemanth Yamijala
> Assignee: Sreekanth Ramakrishnan
> Fix For: 0.21.0
>
> Attachments: mapreduce-682-1.patch, mapreduce-682-2.patch, mapreduce-682-ydist.patch
>
>
> When support was added to reserve tasktrackers for high RAM jobs per MAPREDUCE-516, we missed removing reservations on tasktrackers that are globally blacklisted. This is not a major concern, just that the reservation might cause the job to finish a little later than if the reservation is removed when the blacklisting happens.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.