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 "Gergő Pásztor (JIRA)" <ji...@apache.org> on 2017/01/26 15:44:24 UTC
[jira] [Work started] (MAPREDUCE-6506) Make the reducer-preemption
configs consistent in how they handle defaults
[ https://issues.apache.org/jira/browse/MAPREDUCE-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MAPREDUCE-6506 started by Gergő Pásztor.
------------------------------------------------
> Make the reducer-preemption configs consistent in how they handle defaults
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-6506
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6506
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Components: applicationmaster
> Affects Versions: 2.8.0
> Reporter: Karthik Kambatla
> Assignee: Gergő Pásztor
> Priority: Critical
>
> {{mapreduce.job.reducer.preempt.delay.sec}} and {{mapreduce.job.reducer.unconditional-preempt.delay.sec}} are two configs related to reducer preemption. These configs are not consistent in how they handle non-positive values. Also, the way to disable them is different.
> It would be nice to make them consistent somehow, and change the behavior of former if need be.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org