[
https://issues.apache.org/jira/browse/MAPREDUCE-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556795#comment-13556795
]
Sandy Ryza commented on MAPREDUCE-4929:
---------------------------------------
It doesn't exactly appear that there is precedence behavior in trunk. When a
Configuration#set() is called for a config with deprecations, all the
corresponding configs are set. So if we came across mapred.task.timeout first
in a config file, both mapred.task.timeout and mapreduce.task.timeout would get
set. Then if we came across mapreduce.task.timeout afterwards, both would get
overriden.
> mapreduce.task.timeout is ignored
> ---------------------------------
>
> Key: MAPREDUCE-4929
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4929
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv1
> Affects Versions: 1.1.1
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: MAPREDUCE-4929-branch-1.patch
>
>
> In MR1, only mapred.task.timeout works. Both should be made to work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
