Thanks, I just tried another dataset, which could be successfully handled
by my cluster within memory. However, exceptions still occurred with the
-Dgiraph.useOutOfCoreGraph=true option, but it works fine with only
-Dgiraph.useOutOfCoreMessages=true
option, so do you still think it is the dir
Thanks Claudio. Yes the machines are homogenous. Unfortunately I don't have
ganglia installed. You were right it is a memory issue. I've reduced the
number of partitions down to 1 with -Dgiraph.maxPartitionsInMemory=1 and
now my jobs are failing due to running out of diskspace on HDFS. Each HDFS
Please disregard - Outlook sent it to the wrong address. Sorry. - F
From: Tunvall, Fredrik [mailto:fredrik.tunv...@ovum.com]
Sent: Friday, October 18, 2013 12:25 PM
To: user@giraph.apache.org
Subject: RE: Master always fails on dataset
I will reach out right now
From: Simon McGloin
Dear Claudio Martella,
According to https://reviews.apache.org/r/7990/diff/?page=2, Giraph
currently organize vertices as byte streams, probabily pages.
In the url, This also significantly reduces GC time, as there are less
objects to GC.
Why there's also there? I mean, is reducing GC time the
Da,
Holding objects in serialized form as bytes in byte arrays consumes much
less memory than holding them as Java objects (which have a huge
overhead), I think that is the other main reason for serialization.
--sebastian
On 18.10.2013 19:28, YAN Da wrote:
Dear Claudio Martella,
According
Sorry to be off the topic a bit.
I made my own message structure but was wondering if the received messages
are sorted based on sender id?
I am not able to verify since the call Log.debug() doesn't seem to print
out anything.
Thanks,
Haowei
On Thu, Oct 17, 2013 at 9:31 AM, Sebastian Schelter
