在大数据的当下，各种spark和hadoop的框架层出不穷。各种高端的计算框架，分布式任务如乱花般迷眼。你是否有这种困惑！——有了许多的分布式任务，但是每天需要固定时间跑任务，自己写个调度，既不稳定，又没有可靠的通知。

想要了解Oozie的基础知识，可以参考这里

那么你应该是在找——Oozie。

Oozie是一款支持分布式任务调度的开源框架，它支持很多的分布式任务，比如map reduce,spark,sqoop,pig甚至shell等等。你可以以各种方式调度它们，把它们组成工作流。每个工作流节点可以串行也可以并行执行。

如果你定义好了一系列的任务，就可以开启工作流，设置一个coordinator调度器进行定时的调度了。

有了这些工作以后，还需要一个很重要的环节—— 就是邮件提醒。不管是任务执行成功还是失败，都可以发送邮件提醒。这样每天晚上收到任务成功的消息，就可以安心睡觉了。

因此，本篇就带你来看看如何在Oozie中使用Email。

Email Action

在Oozie中每个工作流的环节都被设计成一个Action，email就是其中的一个Action.

Email action可以在oozie中发送信息，在email action中必须指定接收的地址，主题subject和内容body。在接收地址参数中支持使用逗号分隔，添加多个邮箱地址。

email action是同步执行的，因此必须等到邮件发出后，这个action才算完成，才能执行下一个action。

email action里面的所有参数都可以使用EL表达式。

语法规则

<workflow-app name="[WF-DEF-NAME]" xmlns="uri:oozie:workflow:0.1">

    ...

    <action name="[NODE-NAME]">

        <email xmlns="uri:oozie:email-action:0.2">

            <to>[COMMA-SEPARATED-TO-ADDRESSES]</to>

            <cc>[COMMA-SEPARATED-CC-ADDRESSES]</cc> <!-- cc is optional -->

            <subject>[SUBJECT]</subject>

            <body>[BODY]</body>

            <content_type>[CONTENT-TYPE]</content_type> <!-- content_type is optional -->

            <attachment>[COMMA-SEPARATED-HDFS-FILE-PATHS]</attachment> <!-- attachment is optional -->

        </email>

        <ok to="[NODE-NAME]"/>

        <error to="[NODE-NAME]"/>

    </action>

    ...

</workflow-app>

to和cc命令指定了谁来接收邮件。可以通过逗号分隔来指定多个邮箱地址。to是必填项，cc是可选的。

主题subject和正文body用于指定邮件的标题和正文，email-action:0.2支持text/html这种格式的正文，默认是普通的文本"text/plain"

attachment用于在邮件中添加一个hdfs文件的附件，也可以通过逗号分隔符指定多个附件。如果路径声明的不全，那么也会被当做hdfs中的文件。本地文件是不能添加到附件中的。

配置

email action需要在oozie-site.xml中配置SMTP服务器配置。下面是需要配置的值：

oozie.email.smtp.host

这个值是SMTP服务器的地址，默认是loalhost

oozie.email.smtp.port

是SMTP服务器的端口号，默认是25.

oozie.email.from.address

发送邮件的地址，默认是oozie@localhost

oozie.email.smtp.auth

是否开启认证，默认不开启

oozie.email.smtp.username

如果开启认证，登录的用户名，默认是空

oozie.email.smtp.password

如果开启认证，用户对应的密码，默认是空

PS. 在linux可以通过find -name oozie-site.xml在当前目录下查找。在我们的CDH版本中这个文件在./etc/oozie/conf.dist/oozie-site.xml

遇到的问题

很多人会遇到无法发邮件的问题，首先是要开启SMTP服务，查看是否开启可以使用telnet localhost 25。

另外，如果使用的是企业邮箱，需要注意发件人的格式，必须符合企业邮箱的设置。并且收件人只能是企业邮箱的地址。

在Cloudera Mnager中的配置如下图：

样例

<workflow-app name="sample-wf" xmlns="uri:oozie:workflow:0.1">

    ...

    <action name="an-email">

        <email xmlns="uri:oozie:email-action:0.1">

            <to>bob@initech.com,the.other.bob@initech.com</to>

            <cc>will@initech.com</cc>

            <subject>Email notifications for ${wf:id()}</subject>

            <body>The wf ${wf:id()} successfully completed.</body>

        </email>

        <ok to="myotherjob"/>

        <error to="errorcleanup"/>

    </action>

    ...

</workflow-app>

上面的例子中，邮件发给了bob,the.other.bob以及抄送给will，并指定了邮件的标题和正文以及workflow的id。

附录

为了更多的了解Oozie，这里直接给出了Oozie相关的重要配置

oozie-site.xml配置

<?xml version="1.0"?>

<configuration>

    <!--oozie-default.xml文件是默认的配置-->

    <property>

        <name>oozie.service.ProxyUserService.proxyuser.hue.hosts</name>

        <value>*</value>

    </property>

    <property>

        <name>oozie.service.ProxyUserService.proxyuser.hue.groups</name>

        <value>*</value>

    </property>

</configuration>

oozie-defualt.xml

<?xml version="1.0"?>

<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>

<!--

  Licensed to the Apache Software Foundation (ASF) under one

  or more contributor license agreements.  See the NOTICE file

  distributed with this work for additional information

  regarding copyright ownership.  The ASF licenses this file

  to you under the Apache License, Version 2.0 (the

  distributed under the License is distributed on an "AS IS" BASIS,

  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

  See the License for the specific language governing permissions and

  limitations under the License.

-->

<configuration>

    <!-- ************************** VERY IMPORTANT  ************************** -->

    <!-- This file is in the Oozie configuration directory only for reference. -->

    <!-- It is not loaded by Oozie, Oozie uses its own privatecopy.            -->

    <!-- ************************** VERY IMPORTANT  ************************** -->

    <property>

        <name>oozie.output.compression.codec</name>

        <value>gz</value>

        <description>

            The name of the compression codec to use.

            where codec class implements the interface org.apache.oozie.compression.CompressionCodec.

            If oozie.compression.codecs is not specified, gz codec implementation is used by default.

        </description>

    </property>

    <property>

        <name>oozie.action.mapreduce.uber.jar.enable</name>

        <value>false</value>

        <description>

            which specify the oozie.mapreduce.uber.jar configuration property will fail.

        </description>

    </property>

    <property>

        <name>oozie.processing.timezone</name>

        <value>UTC</value>

        <description>

            is changed, note that GMT(+/-)#### timezones do not observe DST changes.

        </description>

    </property>

    <!-- Base Oozie URL: <SCHEME>://<HOST>:<PORT>/<CONTEXT> -->

    <property>

        <name>oozie.base.url</name>

        <value>http://localhost:8080/oozie</value>

        <description>

             Base Oozie URL.

        </description>

    </property>

    <!-- Services -->

    <property>

        <name>oozie.system.id</name>

        <value>oozie-${user.name}</value>

        <description>

            The Oozie system ID.

        </description>

    </property>

    <property>

        <name>oozie.systemmode</name>

        <value>NORMAL</value>

        <description>

            System mode for  Oozie at startup.

        </description>

    </property>

    <property>

        <name>oozie.delete.runtime.dir.on.shutdown</name>

        <value>true</value>

        <description>

            If the runtime directory should be kept after Oozie shutdowns down.

        </description>

    </property>

    <property>

        <name>oozie.services</name>

        <value>

            org.apache.oozie.service.SchedulerService,

            org.apache.oozie.service.InstrumentationService,

            org.apache.oozie.service.MemoryLocksService,

            org.apache.oozie.service.UUIDService,

            org.apache.oozie.service.ELService,

            org.apache.oozie.service.AuthorizationService,

            org.apache.oozie.service.UserGroupInformationService,

            org.apache.oozie.service.HadoopAccessorService,

/email

            IMPORTANT: if the StoreServicePasswordService is active, it will reset this value with the

value given in

                       the console.

        </description>

    </property>

    <property>

        <name>oozie.service.JPAService.pool.max.active.conn</name>

        <value>10</value>

        <description>

             Max number of connections.

        </description>

    </property>

   <!-- SchemaService -->

    <property>

        <name>oozie.service.SchemaService.wf.schemas</name>

        <value>

            oozie-workflow-0.1.xsd,oozie-workflow-0.2.xsd,oozie-workflow-0.2.5.xsd,oozie-workflow-0.3.x

sd,oozie-workflow-0.4.xsd,

            oozie-workflow-0.4.5.xsd,oozie-workflow-0.5.xsd,

            shell-action-0.1.xsd,shell-action-0.2.xsd,shell-action-0.3.xsd,

            email-action-0.1.xsd,email-action-0.2.xsd,

            hive-action-0.2.xsd,hive-action-0.3.xsd,hive-action-0.4.xsd,hive-action-0.5.xsd,hive-action

-0.6.xsd,

            sqoop-action-0.2.xsd,sqoop-action-0.3.xsd,sqoop-action-0.4.xsd,

            ssh-action-0.1.xsd,ssh-action-0.2.xsd,

            distcp-action-0.1.xsd,distcp-action-0.2.xsd,

            oozie-sla-0.1.xsd,oozie-sla-0.2.xsd,

            hive2-action-0.1.xsd, hive2-action-0.2.xsd,

            spark-action-0.1.xsd,spark-action-0.2.xsd

        </value>

        <description>

            List of schemas for workflows (separated by commas).

        </description>

    </property>

    <property>

        <name>oozie.service.SchemaService.wf.ext.schemas</name>

        <value> </value>

        <description>

            List of additional schemas for workflows (separated by commas).

        </description>

    </property>

    <property>

        <name>oozie.service.SchemaService.coord.schemas</name>

/email

        <description>

             Base console URL for a workflow job.

        </description>

    </property>

    <!-- ActionService -->

    <property>

        <name>oozie.service.ActionService.executor.classes</name>

        <value>

            org.apache.oozie.action.decision.DecisionActionExecutor,

            org.apache.oozie.action.hadoop.JavaActionExecutor,

            org.apache.oozie.action.hadoop.FsActionExecutor,

            org.apache.oozie.action.hadoop.MapReduceActionExecutor,

            org.apache.oozie.action.hadoop.PigActionExecutor,

            org.apache.oozie.action.hadoop.HiveActionExecutor,

            org.apache.oozie.action.hadoop.ShellActionExecutor,

            org.apache.oozie.action.hadoop.SqoopActionExecutor,

            org.apache.oozie.action.hadoop.DistcpActionExecutor,

            org.apache.oozie.action.hadoop.Hive2ActionExecutor,

            org.apache.oozie.action.ssh.SshActionExecutor,

            org.apache.oozie.action.oozie.SubWorkflowActionExecutor,

            org.apache.oozie.action.email.EmailActionExecutor,

            org.apache.oozie.action.hadoop.SparkActionExecutor

        </value>

        <description>

            List of ActionExecutors classes (separated by commas).

            Only action types with associated executors can be used in workflows.

        </description>

    </property>

    <property>

        <name>oozie.service.ActionService.executor.ext.classes</name>

        <value> </value>

        <description>

            List of ActionExecutors extension classes (separated by commas). Only action types with ass

ociated

            executors can be used in workflows. This property is a convenience property to add extensio

ns to the built

            in executors without having to include all the built in ones.

        </description>

    </property>

    <!-- ActionCheckerService -->

    <property>

        <name>oozie.service.ActionCheckerService.action.check.interval</name>

/email

        <description>

            Comma separated AUTHORITY=SPARK_CONF_DIR, where AUTHORITY is the HOST:PORT of

            the ResourceManager of a YARN cluster. The wildcard '*' configuration is

            used when there is no exact match for an authority. The SPARK_CONF_DIR contains

            the relevant spark-defaults.conf properties file. If the path is relative is looked within

            the Oozie configuration directory; though the path can be absolute.  This is only used

            when the Spark master is set to either "yarn-client" or "yarn-cluster".

        </description>

    </property>

    <property>

        <name>oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jar</name>

        <value>true</value>

        <description>

            If true, Oozie will ignore the "spark.yarn.jar" property from any Spark configurations spec

ified in

            oozie.service.SparkConfigurationService.spark.configurations.  If false, Oozie will not ign

ore it.  It is recommended

            to leave this as true because it can interfere with the jars in the Spark sharelib.

        </description>

    </property>

    <property>

        <name>oozie.email.attachment.enabled</name>

        <value>true</value>

        <description>

            This value determines whether to support email attachment of a file on HDFS.

            Set it false if there is any security concern.

        </description>

    </property>

    <property>

        <name>oozie.actions.default.name-node</name>

        <value> </value>

        <description>

            The default value to use for the &lt;name-node&gt; element in applicable action types.  Thi

s value will be used when

            neither the action itself nor the global section specifies a &lt;name-node&gt;.  As expecte

d, it should be of the form

            "hdfs://HOST:PORT".

        </description>

    </property>

    <property>

        <name>oozie.actions.default.job-tracker</name>

        <value> </value>

        <description>

@

search hit BOTTOM, continuing at TOP

            IMPORTANT: if the StoreServicePasswordService is active, it will reset this value with the

value given in

                       the console.

        </description>

    </property>

    <property>

        <name>oozie.service.JPAService.pool.max.active.conn</name>

        <value>10</value>

        <description>

             Max number of connections.

        </description>

    </property>

   <!-- SchemaService -->

    <property>

        <name>oozie.service.SchemaService.wf.schemas</name>

        <value>

            oozie-workflow-0.1.xsd,oozie-workflow-0.2.xsd,oozie-workflow-0.2.5.xsd,oozie-workflow-0.3.x

sd,oozie-workflow-0.4.xsd,

            oozie-workflow-0.4.5.xsd,oozie-workflow-0.5.xsd,

            shell-action-0.1.xsd,shell-action-0.2.xsd,shell-action-0.3.xsd,

            email-action-0.1.xsd,email-action-0.2.xsd,

            hive-action-0.2.xsd,hive-action-0.3.xsd,hive-action-0.4.xsd,hive-action-0.5.xsd,hive-action

-0.6.xsd,

            sqoop-action-0.2.xsd,sqoop-action-0.3.xsd,sqoop-action-0.4.xsd,

            ssh-action-0.1.xsd,ssh-action-0.2.xsd,

            distcp-action-0.1.xsd,distcp-action-0.2.xsd,

            oozie-sla-0.1.xsd,oozie-sla-0.2.xsd,

            hive2-action-0.1.xsd, hive2-action-0.2.xsd,

            spark-action-0.1.xsd,spark-action-0.2.xsd

        </value>

        <description>

            List of schemas for workflows (separated by commas).

        </description>

    </property>

    <property>

        <name>oozie.service.SchemaService.wf.ext.schemas</name>

        <value> </value>

        <description>

            List of additional schemas for workflows (separated by commas).

        </description>

    </property>

    <property>

        <name>oozie.service.SchemaService.coord.schemas</name>

/email

        <description>

             Base console URL for a workflow job.

        </description>

    </property>

    <!-- ActionService -->

    <property>

        <name>oozie.service.ActionService.executor.classes</name>

        <value>

            org.apache.oozie.action.decision.DecisionActionExecutor,

            org.apache.oozie.action.hadoop.JavaActionExecutor,

            org.apache.oozie.action.hadoop.FsActionExecutor,

            org.apache.oozie.action.hadoop.MapReduceActionExecutor,

            org.apache.oozie.action.hadoop.PigActionExecutor,

            org.apache.oozie.action.hadoop.HiveActionExecutor,

            org.apache.oozie.action.hadoop.ShellActionExecutor,

            org.apache.oozie.action.hadoop.SqoopActionExecutor,

            org.apache.oozie.action.hadoop.DistcpActionExecutor,

            org.apache.oozie.action.hadoop.Hive2ActionExecutor,

            org.apache.oozie.action.ssh.SshActionExecutor,

            org.apache.oozie.action.oozie.SubWorkflowActionExecutor,

            org.apache.oozie.action.email.EmailActionExecutor,

            org.apache.oozie.action.hadoop.SparkActionExecutor

        </value>

        <description>

            List of ActionExecutors classes (separated by commas).

            Only action types with associated executors can be used in workflows.

        </description>

    </property>

    <property>

        <name>oozie.service.ActionService.executor.ext.classes</name>

        <value> </value>

        <description>

            List of ActionExecutors extension classes (separated by commas). Only action types with ass

ociated

            executors can be used in workflows. This property is a convenience property to add extensio

ns to the built

            in executors without having to include all the built in ones.

        </description>

    </property>

    <!-- ActionCheckerService -->

    <property>

        <name>oozie.service.ActionCheckerService.action.check.interval</name>

/email

        <description>

            used when there is no exact match for an authority. The SPARK_CONF_DIR contains

            the relevant spark-defaults.conf properties file. If the path is relative is looked within

            the Oozie configuration directory; though the path can be absolute.  This is only used

            when the Spark master is set to either "yarn-client" or "yarn-cluster".

        </description>

    </property>

    <property>

        <name>oozie.service.SparkConfigurationService.spark.configurations.ignore.spark.yarn.jar</name>

        <value>true</value>

        <description>

            If true, Oozie will ignore the "spark.yarn.jar" property from any Spark configurations spec

ified in

            oozie.service.SparkConfigurationService.spark.configurations.  If false, Oozie will not ign

ore it.  It is recommended

            to leave this as true because it can interfere with the jars in the Spark sharelib.

        </description>

    </property>

    <property>

        <name>oozie.email.attachment.enabled</name>

        <value>true</value>

        <description>

            This value determines whether to support email attachment of a file on HDFS.

            Set it false if there is any security concern.

        </description>

    </property>

    <property>

        <name>oozie.actions.default.name-node</name>

        <value> </value>

        <description>

            The default value to use for the &lt;name-node&gt; element in applicable action types.  Thi

s value will be used when

            neither the action itself nor the global section specifies a &lt;name-node&gt;.  As expecte

d, it should be of the form

            "hdfs://HOST:PORT".

        </description>

    </property>

    <property>

        <name>oozie.actions.default.job-tracker</name>

        <value> </value>

        <description>

            The default value to use for the &lt;job-tracker&gt; element in applicable action types.  T

his value will be used when

            neither the action itself nor the global section specifies a &lt;job-tracker&gt;.  As expec

ted, it should be of the form

            "HOST:PORT".

        </description>

    </property>

</configuration>

Oozie分布式任务的工作流——邮件篇的更多相关文章

  1. Oozie分布式任务的工作流——脚本篇

    继前一篇大体上翻译了Email的Action配置,本篇继续看一下Shell的相关配置. Shell Action Shell Action可以执行Shell脚本命令,工作流会等到shell完全执行完毕 ...

  2. Oozie分布式任务的工作流——Spark篇

    Spark是现在应用最广泛的分布式计算框架,oozie支持在它的调度中执行spark.在我的日常工作中,一部分工作就是基于oozie维护好每天的spark离线任务,合理的设计工作流并分配适合的参数对于 ...

  3. Oozie分布式任务的工作流——Sqoop篇

    Sqoop的使用应该是Oozie里面最常用的了,因为很多BI数据分析都是基于业务数据库来做的,因此需要把mysql或者oracle的数据导入到hdfs中再利用mapreduce或者spark进行ETL ...

  4. 分布式协调服务Zookeeper扫盲篇

    分布式协调服务Zookeeper扫盲篇 作者:尹正杰 版权声明:原创作品,谢绝转载!否则将追究法律责任. 身为运维工程师对kubernetes(k8s)可能比较熟,那么etcd(go语言实现)分布式协 ...

  5. [源码解析] PyTorch 分布式(8) -------- DistributedDataParallel之论文篇

    [源码解析] PyTorch 分布式(8) -------- DistributedDataParallel之论文篇 目录 [源码解析] PyTorch 分布式(8) -------- Distrib ...

  6. [源码解析] PyTorch分布式优化器(1)----基石篇

    [源码解析] PyTorch分布式优化器(1)----基石篇 目录 [源码解析] PyTorch分布式优化器(1)----基石篇 0x00 摘要 0x01 从问题出发 1.1 示例 1.2 问题点 0 ...

  7. Oozie分布式工作流——流控制

    最近又开始捅咕上oozie了,所以回头还是翻译一下oozie的文档.文档里面最重要就属这一章了--工作流定义. 一提到工作流,首先想到的应该是工作流都支持哪些工作依赖关系,比如串式的执行,或者一对多, ...

  8. Oozie分布式工作流——Action节点

    前篇讲述了下什么是流控制节点,本篇继续来说一下什么是 Action Nodes操作节点.Action节点有一些比较通用的特性: Action节点是远程的 所有oozie创建的计算和处理任务都是异步的, ...

  9. Oozie分布式工作流——从理论和实践分析使用节点间的参数传递

    Oozie支持Java Action,因此可以自定义很多的功能.本篇就从理论和实践两方面介绍下Java Action的妙用,另外还涉及到oozie中action之间的参数传递. 本文大致分为以下几个部 ...

随机推荐

  1. 2017-1-5 天气雨 React 学习笔记

    官方example 中basic-click-counter <script type="text/babel"> var Counter = React.create ...

  2. CSS HTML元素布局及Display属性

    本篇文章主要介绍HTML的内联元素.块级元素的分类与布局,以及dispaly属性对布局的影响. 目录 1. HTML 元素分类:介绍内联元素.块级元素的分类. 2. HTML 元素布局:介绍内联元素. ...

  3. JavaScript权威指南 - 数组

    JavaScript数组是一种特殊类型的对象. JavaScript数组元素可以为任意类型,最大容纳232-1个元素. JavaScript数组是动态的,有新元素添加时,自动更新length属性. J ...

  4. Android业务组件化之URL Scheme使用

    前言: 最近公司业务发展迅速,单一的项目工程不再适合公司发展需要,所以开始推进公司APP业务组件化,很荣幸自己能够牵头做这件事,经过研究实现组件化的通信方案通过URL Scheme,所以想着现在还是在 ...

  5. C#多线程之基础篇3

    在上一篇C#多线程之基础篇2中,我们主要讲述了确定线程的状态.线程优先级.前台线程和后台线程以及向线程传递参数的知识,在这一篇中我们将讲述如何使用C#的lock关键字锁定线程.使用Monitor锁定线 ...

  6. BPM配置故事之案例13-触发消息通知

    老李:小明! 小明:--见你就没好事,又要我干嘛? 老李:额,小事小事,最近很多部门都觉得Boss的审批速度太慢了,能不能以后给审批人一个消息提醒? 小明:--有一种不太好的预感 老李:怎么,很困难么 ...

  7. iOS微信第三方登录实现

    iOS微信第三方登录实现   一.接入微信第三方登录准备工作.移动应用微信登录是基于OAuth2.0协议标准构建的微信OAuth2.0授权登录系统.在进行微信OAuth2.0授权登录接入之前,在微信开 ...

  8. 15个C++项目列表

    实验楼上有很多C++的实战项目,从简单到进阶,学习每个项目都可以掌握相应的知识点. 如果你还是C++新手的话,那么这个C++的项目列表你可以拿去练手实战开发,毕竟学编程动手实践是少不了的! 如果你不知 ...

  9. Java 进阶 hello world! - 中级程序员之路

    Java 进阶 hello world! - 中级程序员之路 Java是一种跨平台的语言,号称:"一次编写,到处运行",在世界编程语言排行榜中稳居第二名(TIOBE index). ...

  10. SQL Server 2014聚集列存储索引

    转发请注明引用和原文博客(http://www.cnblogs.com/wenBlog) 简介 之前已经写过两篇介绍列存储索引的文章,但是只有非聚集列存储索引,今天再来简单介绍一下聚集的列存储索引,也 ...