[ https://issues.apache.org/jira/browse/GIRAPH-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117891#comment-13117891 ]
Avery Ching commented on GIRAPH-43: ----------------------------------- Yeah, this kind of sucks. One thing we could do is say keep the timers (counters) only for the last n supersteps. This way we don't grow infinitely. I.e use two counters per superstep superstep a = 3 superstep a milliseconds = 70 superstep b = 4 superstep b milliseconds = 71 ... For jobs with a lot of supersteps, we can just grow forever given this limitation. > 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