giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avery Ching (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-52) There should be a scheme to limit the counter
Date Fri, 14 Oct 2011 06:36:12 GMT

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

Avery Ching commented on GIRAPH-52:
-----------------------------------

Anything is probably better than the adhoc counter system we have now. =)  I would certainly
agree that a CounterManager concept that is cleaner would be nice to have and keep us within
the limits of how many counters are available.  I personally would vote for the last n iterations
(sliding window) approach.
                
> There should be a scheme to limit the counter
> ---------------------------------------------
>
>                 Key: GIRAPH-52
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-52
>             Project: Giraph
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.70.0
>            Reporter: Zhiwei Gu
>             Fix For: 0.70.0
>
>
> For hadoop version above 0.20.203.0., the cluster-wise configuration mapreduce.job.counters.limit
cannot be overrided, while the superstep iterations is not deterministic, the job might run
several hundreds or even thousand of supersteps, it will always kill the job. This will limit
the usage of Giraph and is tooooo bad.

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