looks like one of your workers died. If you expect such a long job, I'd suggest you turn checkpointing on.
On Wed, Jan 29, 2014 at 5:30 PM, Jyoti Yadav <[email protected]>wrote: > Thanks all for your reply.. > Actually i am working with an algorithm in which single source shortest > path algorithm runs for thousands of vertices .suppose on an average for > one vertex this algo takes 5-6 supersteps,then for thousands of > vertices,count of superstep is extremely large..In that case at run time > following error is thrown... > > ERROR org.apache.giraph.master.BspServiceMaster: > superstepChosenWorkerAlive: Missing chosen worker > Worker(hostname=kanha-Vostro-1014, MRtaskID=1, port=30001) on superstep > 19528 > 2014-01-28 05:11:36,852 INFO org.apache.giraph.master.MasterThread: > masterThread: Coordination of superstep 19528 took 636.831 seconds ended > with state WORKER_FAILURE and is now on superstep 19528 > 2014-01-28 05:11:39,446 ERROR org.apache.giraph.master.MasterThread: > masterThread: Master algorithm failed with ArrayIndexOutOfBoundsException > java.lang.ArrayIndexOutOfBoundsException: -1 > > Any ideas?? > > Thanks > Jyoti > > > On Wed, Jan 29, 2014 at 8:55 PM, Peter Grman <[email protected]>wrote: > >> Yes but you can disable the counters per superstep, if you don't need the >> data, and than I had around 2000 after which my algorithm stopped. >> >> Cheers >> Peter >> On Jan 29, 2014 4:22 PM, "Claudio Martella" <[email protected]> >> wrote: >> >>> the limit is currently defined by the maximum number of counters your >>> jobtracker allows. Hence, by default the max number of supersteps is around >>> 90. >>> >>> check http://giraph.apache.org/faq.html to see how to increase it. >>> >>> >>> On Wed, Jan 29, 2014 at 4:12 PM, Jyoti Yadav <[email protected] >>> > wrote: >>> >>>> Hi folks.. >>>> >>>> Is there any limit for maximum no of supersteps while running a giraph >>>> job?? >>>> >>>> Thanks >>>> Jyoti >>>> >>> >>> >>> >>> -- >>> Claudio Martella >>> >>> >> > -- Claudio Martella
