hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5680) Reconsider limits
Date Fri, 24 Jan 2014 18:09:41 GMT

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

Ashutosh Chauhan commented on MAPREDUCE-5680:

Whats the word here? Default values are way too low because of reason I outlined above. If
not removing checks altogether, we should atleast consider increasing these super-low limit
values ?

> Reconsider limits
> -----------------
>                 Key: MAPREDUCE-5680
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5680
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: applicationmaster
>    Affects Versions: 2.2.0
>            Reporter: Ashutosh Chauhan
> Limits were first introduced in 0.20.2xx line with the main goal of protecting  jobtracker
from rogue jobs. Now that problem no longer exists in yarn, where each job gets its own MR
AM.  So, its good time now to revisit limits and see which of those still make sense.

This message was sent by Atlassian JIRA

View raw message