hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-3469) Port to 0.22 - Implement limits on per-job JobConf, Counters, StatusReport, Split-Sizes
Date Fri, 07 Feb 2014 23:13:20 GMT

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

Konstantin Shvachko resolved MAPREDUCE-3469.
--------------------------------------------

    Resolution: Duplicate

> Port to 0.22 - Implement limits on per-job JobConf, Counters, StatusReport, Split-Sizes
> ---------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3469
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3469
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Mahadev konar
>            Assignee: Konstantin Shvachko
>              Labels: critical-0.22.0
>
> We have come across issues in production clusters wherein users abuse counters, statusreport
messages and split sizes. One such case was when one of the users had 100 million counters.
This leads to jobtracker going out of memory and being unresponsive. In this jira I am proposing
to put sane limits on the status report length, the number of counters and the size of block
locations returned by the input split. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message