[
https://issues.apache.org/jira/browse/GIRAPH-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127299#comment-13127299
]
Jakob Homan commented on GIRAPH-52:
-----------------------------------
That would be quite reasonable. It could implement either of the schemes above
(or a different one), or for non-limited clusters just churn out the counters.
> 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
