You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Jakob Homan (Resolved) (JIRA)" <ji...@apache.org> on 2011/09/30 07:40:45 UTC
[jira] [Resolved] (GIRAPH-43) GiraphJob: Counter Limit is not set
[ https://issues.apache.org/jira/browse/GIRAPH-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Homan resolved GIRAPH-43.
-------------------------------
Resolution: Not A Problem
Resolving as not a problem, since this is the intended behavior in 203. If it needs to be addressed from Giraph's side, another JIRA can handle it.
> GiraphJob: Counter Limit is not set
> -----------------------------------
>
> Key: GIRAPH-43
> URL: https://issues.apache.org/jira/browse/GIRAPH-43
> Project: Giraph
> Issue Type: Bug
> Components: graph
> Affects Versions: 0.70.0
> Reporter: Severin Corsten
> Priority: Minor
>
> I have got a problem regarding Counters:
> For testing and benchmarking I added a lot of timers bud now the task fails with this Exception:
> org.apache.hadoop.mapred.Counters$CountersExceededException: Error: Exceeded limits on number of counters - Counters=120 Limit=120
> I don't understand why this happens. Within GiraphJob the counter limit is set to 512.
> In the cluster configuration there is no value specified.
--
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