启动作业时出现 oozie 问题
命令：
oozie job -oozie http://localhost:8080/oozie -config /home/hadoop/Desktop/Cloudera/oozie-2.3.0-cdh3u1/examples/apps/no-op/job.properties -run
错误信息：
Error: IO_ERROR : java.net.ConnectException: Connection refused
The command :
oozie job -oozie http://localhost:8080/oozie -config /home/hadoop/Desktop/Cloudera/oozie-2.3.0-cdh3u1/examples/apps/no-op/job.properties -run
Error message:
Error: IO_ERROR : java.net.ConnectException: Connection refused
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
最后我配置了oozie
步骤
在hadoop conf的core-site.xml中添加此行
hadoop.proxyuser.xxx.hosts * hadoop.proxyuser.xxx.groups *
此处，xxx - 用户名
保存conf文件并运行代码
oozie 工作 -oozie http://localhost:11000/oozie -config /home/hadoop/Desktop/ Cloudera/oozie-2.3.0-cdh3u1/examples/apps/no-op/job.properties -run
Finally I configured the oozie
Steps
Add this line in core-site.xml in hadoop conf
hadoop.proxyuser.xxx.hosts * hadoop.proxyuser.xxx.groups *
Here, xxx - User name
Save the conf file and run the code
oozie job -oozie http://localhost:11000/oozie -config /home/hadoop/Desktop/Cloudera/oozie-2.3.0-cdh3u1/examples/apps/no-op/job.properties -run
我花了 2 天时间才修复这个错误。就我而言，我有 4 个节点。 Oozie 是在节点 4 中配置的。但我继续对名称节点（N1）或配置单元服务器（N3）运行命令。因此，请确保您正在针对 Oozie 服务器运行命令。
It took me 2 days to fix this error. In my case I had 4 Nodes. Oozie was configured in Node 4. But I kept on running the command to name-node which was N1 or hive server which was N3. So make sure you are running command against Oozie server.
如果您不是管理员，请确保您从正确的节点调用 oozie 客户端。仅当您从运行 oozie 服务器的计算机连接客户端时才使用
localhost。如果您是像我一样从边缘节点连接的开发人员，请确保导出 oozie 服务器的正确 URL。我在 AWS 上运行的集群（CDH 5.3.6）也遇到了类似的问题。我试图仅使用主机名和端口导出 OOZIE_URL，如下所示，
但它引发了相同的错误。它不喜欢主机名。最后，我导航到 Hue 中的 Oozie 部分（找到最后的步骤），发现 oozie.servers 值
复制了该值并更改了导出命令，如下所示
，这解决了我的问题。
如何查找 oozie.servers 值：
If you are not an Admin make sure you are invoking the oozie client from the correct node. Use
localhostonly if you are connecting the client from the machine where the oozie server is running. If you are a developer like me who is connecting from an edge node make sure you are exporting the correct URL of oozie the server.I had a similar problem in my cluster(CDH 5.3.6) running on AWS. I was trying to export the OOZIE_URL just with the host name and port like below
but it was throwing the same error. It did not like the host name. Finally I have navigated to the Oozie section (find the steps at the end) in Hue and found the oozie.servers value
copied the value and changed the export command like this
and that has fixed my issue.
How to find the oozie.servers value: