In general, have you had a look at the giraph.metrics.enable option? It prints
out metrics after each superstep to each worker's system.out log.
div Ursprüngliche Nachricht /divdivVon: Steven Harenberg
sdhar...@ncsu.edu /divdivDatum:14.01.2015 19:55 (GMT+01:00)
/divdivAn:
Hello everyone,
I have been developing a Giraph application and now wanted to try it on my
four-machine cluster running Hadoop 2.5.1.
My Giraph application is packaged with Giraph 1.1.0-RC1 and all its
dependencies.
I’ve built Giraph and installed it into my local repository using the
14, 2014 at 2:41 PM, Philipp Nolte p...@daslaboratorium.de
wrote:
Hello everyone,
I have been developing a Giraph application and now wanted to try it on my
four-machine cluster running Hadoop 2.5.1.
My Giraph application is packaged with Giraph 1.1.0-RC1 and all its
dependencies
Might have something to do with this Hadoop issue from hadoop 2.3.0
https://issues.apache.org/jira/browse/HADOOP-10451
Quote:
SaslRpcServer.SASL_PROPS is removed.
Any use of this variable should be replaced with the following code:
SaslPropertiesResolver saslPropsResolver =
Might have something to do with this Hadoop issue from hadoop 2.3.0:
https://issues.apache.org/jira/browse/HADOOP-10451
Quote:
SaslRpcServer.SASL_PROPS is removed.
Any use of this variable should be replaced with the following code:
SaslPropertiesResolver saslPropsResolver =
to the ResourceManager, so I don’t quite
understand the error message.
Any ideas? Thanks in advance!
Am 15.12.2014 um 03:31 schrieb Roman Shaposhnik ro...@shaposhnik.org:
On Sun, Dec 14, 2014 at 4:09 PM, Philipp Nolte p...@daslaboratorium.de
wrote:
I’ve had a look at the assembled giraph-core jar file
