[
https://issues.apache.org/jira/browse/MAPREDUCE-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131759#comment-13131759
]
Eli Collins commented on MAPREDUCE-3011:
----------------------------------------
Updating savedLocalDirs is the reason why it runs through the disk checking
code each time. The disk checking is done when newLocalDirs != savedLocalDirs,
and because saveLocalDirs has the bad dirs removed and newLocalDirs is
retrieved from the conf (and per this jira we don't modify the conf) we will
run the disk checking code every time confChanged is called. Make sense?
> TT should remove bad local dirs from conf to prevent constant disk checking
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-3011
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3011
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: tasktracker
> Affects Versions: 0.20.204.0
> Reporter: Eli Collins
>
> Per HADOOP-7551 the TT does not remove bad mapred.local.dirs from the conf so
> after a single disk failure *every* call to get a local path for reading or
> writing results in a disk check of *all* configured local dirs. After
> detecting that a local dir is bad we should remove it from the conf so that
> we don't repeatedly perform this expensive operation.
--
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
