oozie工作流包含fork / join与decesion节点

时间:2018-01-09 06:09:20

标签: oozie-workflow

    <?xml version="1.0" encoding="UTF-8"?>
    <workflow-app xmlns="uri:oozie:workflow:0.5" name="shell-wf">


       <start to="fork_node" />

       <fork name = "fork_node">
          <path start = "query1"/>
          <path start = "query2"/>
       </fork>

       <action name="query1">
          <shell xmlns="uri:oozie:shell-action:0.1">
             <job-tracker>${jobTracker}</job-tracker>
             <name-node>${nameNode}</name-node>
             <configuration>
                <property>
                   <name>mapred.job.queue.name</name>
                   <value>${queueName}</value>
                </property>
             </configuration>
             <exec>oozie.sh</exec>
             <file>oozie.sh#oozie.sh</file>
             <capture-output />
          </shell>
          <ok to="join_node" />
          <error to="postgre"/>
       </action>

       <action name="query2">
          <shell xmlns="uri:oozie:shell-action:0.1">
             <job-tracker>${jobTracker}</job-tracker>
             <name-node>${nameNode}</name-node>
             <configuration>
                <property>
                   <name>mapred.job.queue.name</name>
                   <value>${queueName}</value>
                </property>
             </configuration>
             <exec>oozie2.sh</exec>
             <file>oozie2.sh#oozie2.sh</file>
             <capture-output />
          </shell>
          <ok to="join_node" />
          <error to="postgre" />
       </action>

       <join name = "join_node" to = "postgre"/>

          <action name="postgre">
          <shell xmlns="uri:oozie:shell-action:0.1">
             <job-tracker>${jobTracker}</job-tracker>
             <name-node>${nameNode}</name-node>
             <configuration>
                <property>
                   <name>mapred.job.queue.name</name>
                   <value>${queueName}</value>
                </property>
             </configuration>
             <exec>oozie3.sh</exec>
             <file>oozie3.sh#oozie3.sh</file>
             <capture-output />
          </shell>
          <ok to="decesion-node" />
          <error to="fail" />
       </action>

       <decision name="decesion-node">
            <switch>
                <case to="end">
                  ${wf:lastErrorNode()} eq ""
                </case>
                <default to="fail"/>
            </switch>
        </decision>


        <kill name="fail">
          <message>Action failed, error message[${wf:errorMessage(wf:lastErrorNode())}  ]</message>
       </kill>
       <end name="end" />
    </workflow-app>

尝试运行上述workflow.xml时出现以下错误从节点[decesion-node]到节点[end]的无效转换 - Fork / Join中不允许类型为“end”的节点 我的用例是始终转移到postgre动作而不管作业是否被杀死或成功,一旦执行了postre动作,如果任何动作失败,它应该去杀死节点,否则终止节点。

1 个答案:

答案 0 :(得分:0)

当您在fork join中运行2个MR代码时,它需要在您的群集中使用MR。所以当你运行超过2个MR代码时,它可能会在fork和join中失败。 你可以共享ur * .sh文件,或者你可以检查你是否从你的.sh文件执行普通的shell命令或从shell文件执行任何MR代码。

所以如果你运行MR代码而不是尝试增加你的集群中的MR

谢谢,快乐学习:D