Jakob Homan commented on GIRAPH-43:

Yes, 120 is the default.  It's a cluster config, so it can't be overridden on a 
per job basis (otherwise, everyone would just override it when inconvenient and 
jeopardize the JobTracker).  If you're in charge of the cluster, go ahead and 
modify mapreduce.job.counters.limit in your conf file.  If not, beg and plead 
with whoever is, or consider using fewer counters.
> 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: 
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to