I see more and more people getting into this. I guess whether we should add
the fix to the pure_yarn profile by default, as it feel it's going to stay.
Ideas?
On Sat, Jan 10, 2015 at 7:38 PM, Eugene Koontz ekoo...@hiro-tan.org wrote:
Hi Allesio and Eli,
Compiling with mvn -Phadoop_yarn
Hi Allesio and Eli,
Compiling with mvn -Phadoop_yarn -Dhadoop.version=2.6.0 clean will
avoid the below SASL_PROPS compilation error if you remove the
STATIC_SASL_SYMBOL from the munge.symbols of the hadoop_yarn profile as
follows:
diff --git a/pom.xml b/pom.xml
index cf0e1f9..8c2a561 100644
Hi Alessio,
I am able to reproduce your problem:
https://gist.github.com/ekoontz/7dbaaf6218abb4fd7832
I'll try building Hadoop 2.6.0 and getting Giraph to work with it.
-Eugene
On 1/8/15, 10:55 AM, Eli Reisman wrote:
This looks like a munge symbol that needs to be added to the
hadoop_yarn
This looks like a munge symbol that needs to be added to the hadoop_yarn
profile in the pom.xml. I'm thinking this is an issue a couple people have
been having on 2.5 and 2.6 trying to build the hadoop_yarn profile?
On Thu, Dec 4, 2014 at 1:01 PM, Dr. Alessio Arleo ingar...@icloud.com
wrote:
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”
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 =
Hello everybody
I am trying to compile Giraph release-1.1 for Hadoop 2.5.x and Hadoop 2.6.0
with Maven profile hadoop_yarn. It works fine up to Hadoop 2.4.1, but when
trying with a newer version of Hadoop the following error comes up. I am
working with jdk 1.7 and Maven 3.2.1.
[ERROR]
