Re: Settings : number of workers, heap size. jps showing java tasks even after killing application.

2016-03-24 Thread Anirudh Perugu
Just bumping this thread as I am still looking for answers. On Sun, Mar 20, 2016 at 11:31 AM, Anirudh Perugu < anirudh.per...@stonybrook.edu> wrote: > Hello all, > > This is in follow up to *1. How many workers can I have? * > So I understand that per-worker parallelism is achieved using compute

Re: Settings : number of workers, heap size. jps showing java tasks even after killing application.

2016-03-20 Thread Anirudh Perugu
Hello all, This is in follow up to *1. How many workers can I have? * So I understand that per-worker parallelism is achieved using compute threads. Hence, giraph.numComputeThreads maximum value is limited to # of cores. What is the # of workers limited to? (cannot be 1 for my setup as job runs su

Settings : number of workers, heap size. jps showing java tasks even after killing application.

2016-03-19 Thread Anirudh Perugu
Hello All, I am a giraph newbie, so kindly bear with me. I am trying to run BFS on a graph which has : 28048 edges and 786 nodes. *Here is my Setup :* Single Node Cluster, 8GB RAM, 4 Cores, Apache Yarn 2.7.2, Giraph 1.2.0, my single machine has everything(yarn+giraph) running on it. *1. How many