[
https://issues.apache.org/jira/browse/AMBARI-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193164#comment-14193164
]
Hudson commented on AMBARI-8090:
--------------------------------
SUCCESS: Integrated in Ambari-branch-1.7.0 #284 (See
[https://builds.apache.org/job/Ambari-branch-1.7.0/284/])
AMBARI-8090. Make Oozie memory setting higher with default installation
(aonishuk) (aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dd2a8895f358b6474fa15450635e208d28cf9a61)
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/package/scripts/params.py
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog170Test.java
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/configuration/oozie-env.xml
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java
> Make Oozie memory setting higher with default installation
> ----------------------------------------------------------
>
> Key: AMBARI-8090
> URL: https://issues.apache.org/jira/browse/AMBARI-8090
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 1.7.0
>
>
> PROBLEM: Low Catalina memory setting cause JVM crash. What we saw in JPMC was
> that PID was not cleaned up and Oozie restart via Ambari failed.
> BUSINESS IMPACT: users cannot control Oozie via Ambari
> STEPS TO REPRODUCE: make process run OOM
> SUPPORT ANALYSIS: What we saw in JPMC that the PID failed to cleanup because
> process and pid in /var/run/oozie ran under different process id and
> catalina.out file contained OOM errors.
> We increased memory setting to:
>
>
>
> export CATALINA_OPTS= -Xmx2048m -XX:MaxPermSize=256m
>
> We should set adequate setting with default install.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
