[
https://issues.apache.org/jira/browse/MAPREDUCE-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins resolved MAPREDUCE-2924.
------------------------------------
Resolution: Won't Fix
Thought about this some.. I think leaving the current behavior as is (TT keeps
running regardless # disk failures) but using a health script that shutsdown
the TT when the DN goes down makes more sense. The DN already has logic for
shutting down given a sufficient # of disk failures, and it doesn't make sense
for the TT to keep running if the DN isn't running. Do think we still need to
fix MAPREDUCE-2657, otherwise restarting a cluster may result in a bunch of TTs
that were running not coming up because they tolerated a disk failure while
running but won't while starting.
> TaskTracker number of failed disks to tolerate should be configurable
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-2924
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2924
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: tasktracker
> Affects Versions: 0.20.204.0
> Reporter: Eli Collins
>
> Like HDFS-1161 but for the TT. The user should be able to configure how many
> valid disks are needed for operation. Currently the TT will start and accept
> tasks even if eg only 1 of its 12 disks is working, which leads to poor
> performance of jobs with tasks that use this machine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
