问题描述
试图按照
hadoop版本 - 2.4.0
maven - 3.0.4
sqoop - 1.4.4
在尝试执行bin / mkdistro.sh -DskipTests时失败/>
..........
[INFO] Apache Oozie HCatalog Libs ........ ................ SUCCESS [0.399s]
[INFO] Apache Oozie Core ............... .................. FAILURE [7.819s]
[信息] Apache Oozie Docs ............. .................... SKIPPED
.........
[错误]失败在项目上执行目标oozie-core：无法解析项目org.apache.oozie的依赖关系：oozie-core：jar：4.0.0：下列工件无法解析：org.apache.oozie：oozie-hadoop-test ：jar：2.4.0.oozie-4.0.0，org.apache.oozie：oozie- hadoop：jar：2.4.0.oozie-4.0.0，org.apache.oozie：oozie-sharelib-oozie：jar：4.0.0-cdh5.0.2，org.apache.oozie：oozie-sharelib-hcatalog：jar： 4.0.0-cdh5.0.2：未能找到org.apache.oozie：oozie-hadoop-test：jar：2.4.0.oozie-4.0.0在htp：//repo1.maven.org/maven2缓存在解决方案将不会重新尝试，直到中央的更新间隔已过或强制更新 - > [帮助1] -
[错误] -
[错误]要查看错误的完整堆栈跟踪，使用-e开关重新运行Maven。
[错误]使用-X开关重新运行Maven以启用完整的调试日志记录。
[错误]
[错误]有关错误和可能解决方案的更多信息，请阅读以下文章：
[错误] [帮助1] htp：//cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[错误]
[错误]纠正问题后，你可以恢复
[错误] mvn -rf：oozie-core
有人用hadoop 2.4.0试过oozie4.0.1吗？如何解决这个问题？
我也面临同样的问题。
$ p
$ b
第1步：使用tar提取tar文件-xvf oozie-4.0.1.tar.gz
第2步：使用以下命令将oozie-4.0.1的名称更改为oozie。
mv oozie-4.0.1 oozie
第3步：使用cd oozie / bin移动到oozie / bin目录使用以下命令为
Hadoop-2.2创建oozie。
mkdistro.sh -DskipTests Dhadoopversion = 2
在构建oozie之前，我们必须在pom.xml文件中更改java，hive pig，
sqoop的版本。
Java - 1.7
Hive - 0.13.0
Pig - 0.12.1
Sqoop - 1.4.3
例如：< javaVersion> 1.7< / javaVersion>
< targetJavaVersion> 1.7< / targetJavaVersion>
< hive.version> 0.13.0< /hive.version>
< pig.version> 0.12.1< /pig.version>
< pig.classifier>< /pig.classifier>
< sqoop.version> 1.4.3< /sqoop.version>
如果构建成功，您将收到如
Oozie distro created，DATE [2014.01.05-18：55：14GMT] VC-
REV [不可用]的消息，可在
[/ home / labuser / oozie / distro / target]
现在使用位于
/home/labuser/oozie/distro/target/oozie-4.0.1-distro/oozie-4.0中的扩展oozie .1
第4步：在展开的oozie中创建一个libext目录，并将
Hadoop-2.2.0 jar文件和extjs zip文件复制到libext目录。
第5步：在Hadoop core-site.xml文件中设置此属性。
例如：< property>
< name> hadoop.proxyuser.labuser.hosts< / name>
<值> *< /值>
< / property>
<属性>
< name> hadoop.proxyuser.labuser.groups< / name>
<值> *< /值>
< / property>
在位于conf目录
< name> oozie.service.JPAService.create.db.schema< / name>中的oozie-site.xml文件中设置此属性。
<值> true< /值>
默认为false，将其更改为true
步骤6：现在准备一个oozie war文件。所以移到扩展的oozie / bin
并运行下面的命令。
./oozie-setup.sh prepare-war
如果你得到任何类似zip的命令：command not found，那么使用下面的命令安装
zip sudo apt-get install zip
然后再次运行prepare-war命令来创建一个文件。如果
war文件成功创建，您将收到如
的消息INFO：Oozie已准备好启动
步骤7：将share lib文件夹从扩展的oozie上传到hdfs，使用
下面的命令
./oozie-setup.sh sharelib创建-fs hdfs：// localhost：8020
第8步：使用命令
./oozie-setup为oozie创建一个数据库。 sh db create -run
如果创建了数据库，您将收到如
设置的消息CATALINA_OPTS =$ CATALINA_OPTS -Xmx1024m
验证数据库连接
DONE
检查数据库schema不存在
DONE
检查OOZIE_SYS表不存在
DONE
创建SQL模式
DONE
创建OOZIE_SYS表
DONE
为Oozie版本'4.0.0'创建Oozie DB
步骤9：使用./oozied.sh启动oozie start
第10步：检查oozie使用下面的命令
./oozie admin -oozie http：// localhost：11000 / oozie -status
你会得到如系统模式的信息：NORMAL
问题面对这个安装
1.在构建hive-0.13时。 0共享Oozie库，有一个无法解决的依赖'hive-builtins'。
原因：Hive-builtins jar在hive-0.10.0中是必需的，但是在hive-0.13.0中没有hive-builtins.jar。
解决方案：删除依赖项hive-builtins
2.在构建Oozie时，我们遇到了java.lang.OutOfMemoryError
的问题原因：此错误表示运行Maven的JVM内存不足。它是由maven-compiler-plugin
引起的解决方案：编辑一个maven-compiler-plugin属性
< fork> true< / fork>
Fork允许在单独的进程中运行编译器。如果为false，则使用内置编译器;如果为true，则使用可执行文件。
最后，我们制作了一个Oozie bulid，以上版本的Hadoop生态系统。
Trying to install oozie 4.0.1 following http://www.thecloudavenue.com/2013/10/installation-and-configuration-of.html
hadoop version - 2.4.0
maven - 3.0.4
sqoop - 1.4.4
while trying to execute "bin/mkdistro.sh -DskipTests", failed building
..........
[INFO] Apache Oozie HCatalog Libs ........................ SUCCESS [0.399s]
[INFO] Apache Oozie Core ................................. FAILURE [7.819s]
[INFO] Apache Oozie Docs ................................. SKIPPED
.........
[ERROR] Failed to execute goal on project oozie-core: Could not resolve dependencies for project org.apache.oozie:oozie-core:jar:4.0.0: The following artifacts could not be resolved: org.apache.oozie:oozie-hadoop-test:jar:2.4.0.oozie-4.0.0, org.apache.oozie:oozie-hadoop:jar:2.4.0.oozie-4.0.0, org.apache.oozie:oozie-sharelib-oozie:jar:4.0.0-cdh5.0.2, org.apache.oozie:oozie-sharelib-hcatalog:jar:4.0.0-cdh5.0.2: Failure to find org.apache.oozie:oozie-hadoop-test:jar:2.4.0.oozie-4.0.0 in htp://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] htp://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :oozie-core
anybody tried oozie4.0.1 with hadoop 2.4.0? how can I solve this issue?
Me too faced the same probelm.
Try this installtion steps it is worked for me change the versions in below steps depends on what version you need.
STEP 1 : Extract the tar file using tar -xvf oozie-4.0.1.tar.gz
STEP 2 : Change the name oozie-4.0.1 to oozie using below command.
mv oozie-4.0.1 oozie
STEP 3 : Move to oozie/bin directory using cd oozie/bin Build oozie for
Hadoop-2.2 using below command.
mkdistro.sh -DskipTests Dhadoopversion=2
Before build oozie we must change versions for java, hive pig,
sqoop in pom.xml file.
Java - 1.7
Hive - 0.13.0
Pig - 0.12.1
Sqoop - 1.4.3
Eg : <javaVersion>1.7</javaVersion>
<targetJavaVersion>1.7</targetJavaVersion>
<hive.version>0.13.0</hive.version>
<pig.version>0.12.1</pig.version>
<pig.classifier></pig.classifier>
<sqoop.version>1.4.3</sqoop.version>
If build is success you will get the message like
Oozie distro created, DATE[2014.01.05-18:55:14GMT] VC-
REV[unavailable], available at
[/home/labuser/oozie/distro/target]
Now use the expanded oozie located in
/home/labuser/oozie/distro/target/oozie-4.0.1-distro/oozie-4.0.1
STEP 4 : Create a libext directory in expanded oozie and copy the
Hadoop-2.2.0 jar files and extjs zip file to libext directory.
STEP 5 : Set this property in Hadoop core-site.xml file.
Eg : <property>
<name>hadoop.proxyuser.labuser.hosts</name>
<value>*</value>
</property>
<property>
<name>hadoop.proxyuser.labuser.groups</name>
<value>*</value>
</property>
Set this property in oozie-site.xml file located in conf directory
<name>oozie.service.JPAService.create.db.schema</name>
<value>true</value>
By default it is false change it to true
Step 6 : Now prepare a oozie war file. So move to expanded oozie/bin
and run the below command.
./oozie-setup.sh prepare-war
If you get any error like zip: command not found then install
zip using following command sudo apt-get install zip
Then again run the prepare-war command to create a file. if the
war file created successfully you will get the message like
INFO: Oozie is ready to be started
Step 7 : upload the share lib folder from expanded oozie to hdfs using the
below command
./oozie-setup.sh sharelib create -fs hdfs://localhost:8020
Step 8 : Create a database for oozie using the command
./oozie-setup.sh db create –run
If database created then you will get the message like
setting CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m"
Validate DB Connection
DONE
Check DB schema does not exist
DONE
Check OOZIE_SYS table does not exist
DONE
Create SQL schema
DONE
Create OOZIE_SYS table
DONE
Oozie DB has been created for Oozie version ’4.0.0′
Step 9 : Start the oozie using ./oozied.sh start
Step 10 : Check status of oozie using the below command
./oozie admin –oozie http://localhost:11000/oozie -status
You will get the message like System mode: NORMAL
Issues Faced with this installation
1. While building hive-0.13.0 share library of Oozie, there is an unsolvable dependency ‘hive-builtins’.
Cause: Hive-builtins jar is necessary in hive-0.10.0 but in hive-0.13.0 there is no hive-builtins.jar.
Solution: Removed dependency hive-builtins
2. While building Oozie, we faced issue with java.lang.OutOfMemoryError
Cause: This error signals that the JVM running Maven has run out of memory. It is caused by maven-compiler-plugin
Solution: Edited a maven-compiler-plugin property
<fork>true</fork>
Fork allows running the compiler in a separate process. If false it uses the built in compiler, while if true it will use an executable.
Finally we made a Oozie bulid, with above versions of Hadoop-ecosystems.
这篇关于尝试执行“bin / mkdistro.sh -DskipTests”时出现Oozie错误。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！