I have managed to compile Giraph 1.1.0 for hadoop 2.5.1 with YARN (without STATIC_SASL) but have not yet got it to work on my cluster (neither YARN nor MR).
Off-topic: Its a bit frustrating. I really had my hopes up on Giraph 1.1.0. YARN has been the default for hadoop for quite a while now. Lets just hope t hat Giraph manages to catch up soon or people will be looking at other solutions.
I can’t roll back the cluster to Hadoop 2.0.3 (Giraph apparently works for that version with YARN), so I just have to keep trying to get it to work with MapReduce.
Thank you very much Philipp for your kind answer :) In the end I managed to compile giraph 1.1 for hadoop 2.6.0 on PURE_YARN profile by removing the STATIC_SASL_SYMBOL but when I tried to run the example algorithms the computation resulted in an error (a container returned a mysterious “127” error code). To be honest, for me Giraph 1.1.0 is not working at all (even when building it on the hadoop_2 or hadoop_1 profiles), on Yarn and on MR either; I had to rollback to Giraph 1.0.0 on Hadoop 1.2.0 to be able at least to run the shortest path example. But that’s off-topic.
I think that this issue could be marked as “resolved” because I was able to build it in the end, but I am not sure that the software built is a working jar.
Dott. Alessio Arleo
Dottorando in Ingegneria Industriale e dell’Informazione
Dottore in Ingegneria Informatica ed Elettronica
Dottore Magistrale in Ingegneria Informatica e dell’Automazione
Skype: Dr. Alessio Arleo
Tel: +39 075 5853920
Cell: +39 349 0575782
Might have something to do with this Hadoop issue from hadoop 2.3.0:
"SaslRpcServer.SASL_PROPS is removed.
Any use of this variable should be replaced with the following code:
SaslPropertiesResolver saslPropsResolver = SaslPropertiesResolver.getInstance(conf);
Map<String, String> sasl_props = saslPropsResolver.getDefaultProperties();“
If you want to still compile, compile without the
To do so, change the following line 1197 of the pom.xml in the giraph parent directory from