You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/09/12 17:51:33 UTC

[jira] [Commented] (AMBARI-7283) Oozie config backward in compatible change in HDP2.2

    [ https://issues.apache.org/jira/browse/AMBARI-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131674#comment-14131674 ] 

Hudson commented on AMBARI-7283:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #231 (See [https://builds.apache.org/job/Ambari-trunk-Commit/231/])
AMBARI-7283 Oozie config backward in compatible change in HDP2.2 (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6aeb3be27c4f0f9abc473cd388e954f41fe5172a)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/OOZIE/configuration/oozie-site.xml


> Oozie config backward in compatible change in HDP2.2
> ----------------------------------------------------
>
>                 Key: AMBARI-7283
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7283
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 1.7.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 1.7.0
>
>
> https://issues.apache.org/jira/browse/OOZIE-1680
> Causes any coord whose frequency is faster than 5 mins to fail. In order to avoid that you have to set oozie.service.coord.check.maximum.frequency to false.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)