Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 19 May 2016 05:31:12 +0000 (UTC)
From: "Weiqing Yang (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12971009.1463635819000.232437.1463635872881@Atlassian.JIRA>
In-Reply-To: <JIRA.12971009.1463635819000@Atlassian.JIRA>
References: <JIRA.12971009.1463635819000@Atlassian.JIRA> <JIRA.12971009.1463635819659@arcas>
Subject: [jira] [Created] (AMBARI-16757) Spark History Server heap size is
 not exposed (History Server crashed with OOM)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 19 May 2016 05:31:14 -0000

Weiqing Yang created AMBARI-16757:
-------------------------------------

             Summary: Spark History Server heap size is not exposed (History Server crashed with OOM)
                 Key: AMBARI-16757
                 URL: https://issues.apache.org/jira/browse/AMBARI-16757
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.0.0
            Reporter: Weiqing Yang
            Priority: Critical
             Fix For: 2.4.0


Ambari is not exposing the heap size parameter for Spark History Server.
The workaround is to modify spark-env and add "SPARK_DAEMON_MEMORY=2g" for example.
The newer versions of Spark defaults this to 1g, but on the older versions, it was defaulting to 512m it seems, and it was causing OOM.
So in the patch, "SPARK_DAEMON_MEMORY=1G" is added in the spark-env template (default: 1G).


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