You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2014/11/01 18:07:34 UTC
[jira] [Updated] (AMBARI-8090) Make Oozie memory setting higher
with default installation
[ https://issues.apache.org/jira/browse/AMBARI-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated AMBARI-8090:
----------------------------------
Description:
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 int 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.
was:
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.
> 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 int 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)