incubator-giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (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:42:12 GMT

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

Jakob Homan commented on GIRAPH-52:
-----------------------------------

I'm not sure sliding window will work, since there's no way to remote counters once they're
set.  We're limited to n total for the whole job.  

Also, for the MR2 work, it would be good to code against an interface so that once MR and
its notions of counters are gone, we can have a different implementation in the new framework
(although at that point, we can remove this limit itself).
                
> 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