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

Posted to issues@ambari.apache.org by "Di Li (JIRA)" <ji...@apache.org> on 2017/07/21 20:11:00 UTC

[jira] [Commented] (AMBARI-21553) Oozie server failed to restart post IOP 4.2 migration

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

Di Li commented on AMBARI-21553:
--------------------------------

pushed to branch-2.5 as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=2441f68ab6ea54c7ea30e0ae1a01ff9866d04106

> Oozie server failed to restart post IOP 4.2 migration
> -----------------------------------------------------
>
>                 Key: AMBARI-21553
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21553
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.2
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21553.patch
>
>
> This is after the manual workaround of installing extjs from HDP-UTIL to replace the one from IOP-UTIL - AMBARI-21463
> This is due to the deprecated -Xms oozie_initial_heapsize property in oozie-env



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)