[ 
https://issues.apache.org/jira/browse/HADOOP-11790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390381#comment-15390381
 ] 

Allen Wittenauer commented on HADOOP-11790:
-------------------------------------------

OK, this problem is way worse than just test cases failing. (Although that bit 
does make it particularly hard to run nightlies on the ASF PowerPC box.)

leveldb is starting to go into several key bits of Apache Hadoop, especially in 
YARN.

Raising the priority of this, because this makes Hadoop pretty much unusable 
out of the box without building your own leveldb library and getting  
java.library.path set appropriately.  

Right now, the known breakage is:

* NodeManager
* Timeline Server
* HDFS OIV
* ResourceManager
* JHS

So primarily YARN.

> leveldb usage should be disabled by default or smarter about platforms
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-11790
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11790
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>         Environment: * any non-x86
> * any OS that isn't Linux, OSX, Windows
>            Reporter: Ayappan
>            Priority: Critical
>
> The leveldbjni artifact in maven repository has been built for only x86 
> architecture. Due to which some of the testcases are failing in PowerPC. The 
> leveldbjni community has no plans to support other platforms [ 
> https://github.com/fusesource/leveldbjni/issues/54 ]. Right now , the 
> approach is we need to locally built leveldbjni prior to running hadoop 
> testcases. Pushing a PowerPC-specific leveldbjni artifact in central maven 
> repository and making pom.xml to pickup it up while running in PowerPC is 
> another option but i don't know whether this is a suitable one . Any other 
> alternative/solution is there ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to