Other folks on the list are also having this problem with the progressable
utile exception job failures. I don't know much about master compute
usage but if it is needed to make the aggregators work, maybe we should
have a default dummy class that just handles aggregators if no other master
Hi Tu,
first of all, I really suggest you run trunk, especially if you have a
large graph. That being said:
1) yes and no, the jargon is misleading. you should have n - 1 workers
(what you call mappers for giraph job) with n as the max number of mappers
you can have in your cluster as an upper
Eugene:
Not a obvious question and I should have mentioned in my post that
I have
been running a number of other tests and engines on this cluster (Hive,
Pig, Mahout,
JCuda, etc.) successfully.
On 2/14/2013 4:09 PM, Eugene Koontz wrote:
Hi David,
Please forgive this obvious
Hi Claudio,
Thank you very much for your valuable inputs. I will follow your suggestions to
try giraph 0.2 ( from trunk ) and the workers setting.
Min
From: Claudio Martella
claudio.marte...@gmail.commailto:claudio.marte...@gmail.com
Reply-To:
On 2/14/13 11:36 AM, David Boyd wrote:
All:
I have seen some traffic in the archives of this list about this
topic but not the specific problem I am seeing.
I have CDH 4.1.1 installed on my cluster and my client machine.
After several attempts at building Giraph directly I came across
Progressable exception can be caused by many different reasons (it's totally
unrelated to aggregators), and when looking at which exception it's caused by
users should get better sense about what's going on.
What you are suggesting about providing default master compute is not doable,
since the
