hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2835) Make per-job counter limits configurable
Date Wed, 15 Feb 2012 18:08:59 GMT

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

Harsh J commented on MAPREDUCE-2835:
------------------------------------

I agree with Brian's reasoning.

I understand that if you place a configuration and a newbie user/ops encounters it, they'll
just raise it without second consideration. We need to address such best practices with docs/warn
logs (logs can warn with hard numbers), rather than magic numbers that would not fit every
one/every case.
                
> Make per-job counter limits configurable
> ----------------------------------------
>
>                 Key: MAPREDUCE-2835
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2835
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.20.204.0
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: MAPREDUCE-2835.patch, MAPREDUCE-2835.patch
>
>
> The per-job counter limits introduced in MAPREDUCE-1943 are fixed, except for the total
number allowed per job (mapreduce.job.counters.limit). It would be useful to make them all
configurable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message