hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-6506) Make the reducer-preemption configs consistent in how they handle defaults
Date Thu, 02 Feb 2017 23:28:51 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karthik Kambatla resolved MAPREDUCE-6506.
-----------------------------------------
          Resolution: Not A Problem
    Target Version/s:   (was: )

Closing this as "Not a Problem". 

As Haibo mentioned, setting both configs to a negative value disables the individual features.
It is just that disabling one means preempting instantly and disabling another means preempting
never. 

> 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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org


Mime
View raw message