Thanks Xenia.I also managed to solve the issue. Following is how I solved it.
I ran netstat on all the computers of my cluster, and I ran the gripah job in
parallel.I then learnt that this process runs on 127.0.0.1 while other machine
tries to connect on 172.21.xx.xxx. That's why It gives the
Hi All,In my algo, I use an Aggregator which takes a Text value. I have written
my custom aggregator class for this, as given below.
public class MyAgg extends BasicAggregatorText {...}
This works fine when running on my laptop with one worker.However, when running
it on the cluster, sometimes
Hi Tripti,
finally I was able to run the test with success. It was an issue of permission
since I was running as ale not as yarn.
Let me say that now I’m able to run graph examples on Yarn 2.5.1. This is the
final result:
14/11/08 16:24:00 INFO yarn.GiraphYarnClient: Completed Giraph:
Hi all,
I have a question related to my last experience using Giraph.
In Giraph worker's code, I see a line like this:
*getServerData().getCurrentMessageStore().writePartition(verticesOutputStream,
partition.getId());*
To the best of my knowledge, while executing this line, a worker writes
