[
https://issues.apache.org/jira/browse/MAPREDUCE-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839881#comment-15839881
]
Gergő Pásztor commented on MAPREDUCE-6506:
------------------------------------------
Current state:
mapreduce.job.reducer.preempt.delay.sec:
- minus or zero: preempt instantly
- plus: use the delay time
mapreduce.job.reducer.unconditional-preempt.delay.sec
- minus: disable this feature
- zero: preempt instantly
- plus: use the delay time
I can modify the "mapreduce.job.reducer.preempt.delay.sec" settings, so minus
number means disabling the feature. My concern is that this change also means
that we won't run the preemption if both config is disabled.
> 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: [email protected]
For additional commands, e-mail: [email protected]
