keep in mind that you can also increase the maximum number of counters for your hadoop cluster (i.e. via mapreduce.job.counters.limit).
On Sat, Nov 15, 2014 at 2:04 AM, Charith Wickramarachchi < charith.dhanus...@gmail.com> wrote: > I was thinking more from a functionality point of view. And I think it is > a must fix bug. As you pointed out, this is an old issue and seems like > It was ignored for a long time. > > I found that one work around is to use giraph.useSuperstepCounters=false > option. So I am fine with that. > > Thanks, > Charith > > > On Fri, Nov 14, 2014 at 1:17 PM, Roman Shaposhnik <ro...@shaposhnik.org> > wrote: > >> On Thu, Nov 13, 2014 at 6:35 PM, Charith Wickramarachchi >> <charith.dhanus...@gmail.com> wrote: >> > Hi, >> > >> > Is https://issues.apache.org/jira/browse/GIRAPH-52 fixed in this >> version? Or >> > is there a work around. >> > I think it is a blocker. >> >> I honestly can't see how an issue that is that old could be a blocker. >> >> Thanks, >> Roman. >> > > > > -- > Charith Dhanushka Wickramaarachchi > > Tel +1 213 447 4253 > Blog http://charith.wickramaarachchi.org/ > <http://charithwiki.blogspot.com/> > Twitter @charithwiki <https://twitter.com/charithwiki> > > This communication may contain privileged or other confidential information > and is intended exclusively for the addressee/s. If you are not the > intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should > not print, copy, retransmit, disseminate, or otherwise use the > information contained in this communication. Internet communications > cannot be guaranteed to be timely, secure, error or virus-free. The > sender does not accept liability for any errors or omissions > -- Claudio Martella
