Hi Edward, Unfortunately I don't know what the problem. If you are curious enough to reproduce, you may checkout my project from github at this commit: https://github.com/willmore/hama-kmeans/commit/5d629fbd998e86116890234fdf5ee2b95451dec4
The project is built with maven, so it should be quick to build and deploy. Arguments to the main method are: <num_points> <num_clusters> where num_clusters must <= number of grooms. -Chris ________________________________ From: Edward J. Yoon <[email protected]> To: [email protected]; Chris Willmore <[email protected]> Sent: Monday, May 23, 2011 3:21 AM Subject: Re: Fixed: hama-0.2 Job blocking after all tasks completed That's great. By the way, what was problem? On Mon, May 23, 2011 at 3:51 AM, Chris Willmore <[email protected]> wrote: > Hi All, > > I simplified my algorithm and the issue has disappeared. > > Regards, > Chris > > > > ________________________________ > From: Chris Willmore <[email protected]> > To: "[email protected]" <[email protected]> > Sent: Sunday, May 22, 2011 5:17 PM > Subject: hama-0.2 Job blocking after all tasks completed > > > Hi Folks, > > I am running hama-0.2 with 3 groomservers, on 3 hosts. I submit the job via > the hama command interface, and it seems to execute perfectly. Tailing of the > groom server logs shows succesfull completion. The forked GroomServer.Child > processes shutdown, but the job never fully completes. > On the BSPMaster, running jstack on the hama.util.RunJar process shows the > main thread still blocked on BSPJob.waitForCompletion(true). > > I've looked through the logs of master, zookeeper, and grooms and everything > looks good afaik. > > Here is the source of my program: > https://github.com/willmore/hama-kmeans/blob/master/src/main/java/ee/ut/cs/willmore/KMeansCluster.java > > > Any pointers would be greatly appreciated. > > Cheers, > Chris -- Best Regards, Edward J. Yoon @eddieyoon
