Great !
--
*José Luis Larroque*
Analista Programador Universitario - Facultad de Informática - UNLP
Desarrollador Java y .NET en LIFIA
2017-02-20 6:35 GMT-03:00 Sai Ganesh Muthuraman :
> Hi Jose,
>
> Thanks for that, I used *javac -source 1.7 -target 1.7* and it worked for
> me.
>
> Sai Ganesh
Hi Jose,
Thanks for that, I used **javac -source 1.7 -target 1.7** and it worked for me.
Sai Ganesh
Maybe your problem isn't related to Giraph and Yarn, look at this:
http://stackoverflow.com/questions/22489398/unsupported-major-minor-version-52-0
You should look at what version of Giraph do you use for compiling it and
compare with the version that you are using at runtime in the cluster.
Bye
Hi Jose,
In fact, this is the running status of the application
17/02/16 21:52:27 INFO yarn.GiraphYarnClient: Giraph:
hu.elte.inf.mbalassi.msc.giraph.betweenness.BetweennessComputation, Elapsed:
0.86 secs
17/02/16 21:52:27 INFO yarn.GiraphYarnClient:
appattempt_1487310728133_0001_01, Stat
Hi user,
As I said before, I am using the XSEDE comet cluster which has the following
specifications
**Number of cores per node - 24**
**Memory per node - 128 GB**
The file system is NFS, hence there is nothing like number of disks per
machine.
I went through the previous discussions, but
Hi Sai, your question is like "the question" for using Giraph.
Those resources depends on how much memory do you have on every node, it
depends if the cluster it's used for another user at the same time, depends
on the type of program that you are running, etc. Virtual memory can be
easily increas
Hi,
I am trying to run a giraph application (computing betweenness centrality) in
the XSEDE comet cluster. But everytime I get some error relating to container
launch. Either the virtual memory or physical memory is running out.
The avoid this, it looks like that the following parameters have
