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 "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/22 07:25:58 UTC

[jira] [Commented] (MAPREDUCE-6721) mapreduce.reduce.shuffle.memory.limit.percent=0.0 should be legal to enforce shuffle to disk

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343844#comment-15343844 ] 

ASF GitHub Bot commented on MAPREDUCE-6721:
-------------------------------------------

GitHub user gerashegalov opened a pull request:

    https://github.com/apache/hadoop/pull/102

    MAPREDUCE-6721.001

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gerashegalov/hadoop feature/MAPREDUCE-6721

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hadoop/pull/102.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #102
    
----
commit a41affd11e122eabd6587b92d704fe3c10f315d4
Author: Gera Shegalov <ge...@apache.org>
Date:   2016-06-22T07:20:35Z

    MAPREDUCE-6721.001

----


> mapreduce.reduce.shuffle.memory.limit.percent=0.0 should be legal to enforce shuffle to disk
> --------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6721
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6721
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, task
>    Affects Versions: 2.6.4
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>
> We are potentially hitting an in-memory-shuffle-related reservation starvation resembling MAPREDUCE-6445. To work it around, we wanted to disable in memory shuffle via mapreduce.reduce.shuffle.memory.limit.percent=0.0 that turned out to be disallowed by the current logic. So we had to resort to another small float value such as 0.0001. However, zero is more logical imo.



--
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