简体   繁体   English

Oozie 错误:E1310:E1310:捆绑作业提交错误:[null]

[英]Oozie Error: E1310 : E1310: Bundle Job submission Error: [null]

I created a oozie bundle consisting of several coordinators and respective workflows.我创建了一个 oozie 包,由几个协调器和各自的工作流程组成。 The bundle ran fine previously but with adding a new workflow it stopped working completely.捆绑包以前运行良好,但添加新工作流程后,它完全停止工作。

For simplification and debugging I stripped the bundle down to the absolute minimum consisting of one coordinator starting one workflow.为了简化和调试,我将捆绑包缩减到绝对最小值,由一名协调员启动一个工作流程。

The XMLs seem to be valid (validated with oozie) and the coordinator and workflow is working fine on their own (with fitting properties). XML 似乎是有效的(使用 oozie 验证),并且协调器和工作流本身工作正常(具有拟合属性)。

Problem is, that I do not get any meaningful errors on -dryrun or run.问题是,我在 -dryrun 或 run 上没有收到任何有意义的错误。 Dryrun is producing the error: Error: E1310 : E1310: Bundle Job submission Error: [null] which does not lead me anywhere. Dryrun 正在产生错误: Error: E1310 : E1310: Bundle Job submission Error: [null]这并没有引导我到任何地方。

Just running the job results in the bundle being submitted and markes as "FAILED" with no coordinator started.仅运行作业会导致提交包并标记为“失败”,而没有启动协调器。 Therefore I do not get any error reports on the coordinator to work with.因此,我没有收到关于协调器的任何错误报告。

After playing around with the coordinator and workflow and the propagation of the variables from the bundle.properties file to the coordinator and the workflow I found a couple of important things to take note of that solved my problem in the end:在玩弄协调器和工作流以及将变量从 bundle.properties 文件传播到协调器和工作流之后,我发现了一些需要注意的重要事项,最终解决了我的问题:

  1. -dryrun on a bundle does not work as intended it seems. -dryrun 在捆绑包上似乎没有按预期工作。 The above error is persistent even after fixing the bundle to run fine in oozie.即使在修复包以在 oozie 中正常运行后,上述错误仍然存​​在。 I could not find anything noting that dryrun is not supported on bundles but the [null] is indicating that dryrun can not handle bundles我找不到任何说明捆绑包不支持dryrun 但[null]表示dryrun 无法处理捆绑包的内容
  2. HDFS Paths have to be added with port numbers to work correctly. HDFS 路径必须添加端口号才能正常工作。 I had several paths in the format of hdfs://nodename/hdfs/dir/.... that did not seem to be propagated correctly without the correct path in the format of hdfs://nodename:8020/hdfs/dir/... .我有几个格式为hdfs://nodename/hdfs/dir/....的路径,如果没有格式为hdfs://nodename:8020/hdfs/dir/... After adding the portnumber they worked fine添加端口号后,他们工作正常
  3. I missed a couple of variables in the bundle.xml that were used in the coordinator.xml.我错过了在 coordinator.xml 中使用的 bundle.xml 中的几个变量。 This did not get reported by oozie at all but instead followed in the coordinator not being started at all.这根本没有被 oozie 报告,而是在协调器根本没有启动时被跟踪。 The bundle will just be listed with -info without any sheduled coordinators with the status "running".该包将仅与 -info 一起列出,而没有任何状态为“正在运行”的调度协调器。 This is pretty hard to debug because of missing feedback on oozie.由于缺少对 oozie 的反馈,这很难调试。 Make sure to test your coordinator with a properties file and use that "working" properties file as a schema to check the bundle.properties and .xml for any missed variable确保使用属性文件测试您的协调器,并使用该“工作”属性文件作为架构来检查 bundle.properties 和 .xml 是否有任何遗漏的变量

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM