spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nuno Azevedo (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SPARK-25552) Upgrade from Spark 1.6.3 to 2.3.0 seems to make jobs use about 50% more memory
Date Thu, 27 Sep 2018 10:23:00 GMT

     [ https://issues.apache.org/jira/browse/SPARK-25552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nuno Azevedo updated SPARK-25552:
---------------------------------
    Environment: 
Original found in an AWS Kubernetes environment with Spark Embedded.

 

Also happens in a small scale both with Linux and MacOS.

  was:
AWS Kubernetes

Spark Embedded


> Upgrade from Spark 1.6.3 to 2.3.0 seems to make jobs use about 50% more memory
> ------------------------------------------------------------------------------
>
>                 Key: SPARK-25552
>                 URL: https://issues.apache.org/jira/browse/SPARK-25552
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.3.0
>         Environment: Original found in an AWS Kubernetes environment with Spark Embedded.
>  
> Also happens in a small scale both with Linux and MacOS.
>            Reporter: Nuno Azevedo
>            Priority: Major
>         Attachments: Spark1.6-50GB.png, Spark2.3-50GB.png, Spark2.3-70GB.png
>
>
> After upgrading from Spark 1.6.3 to 2.3.0 our jobs started to need about 50% more memory
to run.
>  
> For instance, before we were running a job with Spark 1.6.3 and it was running fine with
50 GB of memory.
> !Spark1.6-50GB.png|width=800,height=456!
>  
> After upgrading to Spark 2.3.0, when running the same job again with the same 50 GB of
memory it failed due to out of memory.
> !Spark2.3-50GB.png|width=800,height=366!
>  
> Then, we started incrementing the memory until we were able to run the job, which was
with 70 GB.
> !Spark2.3-70GB.png|width=800,height=366!
>  
> The Spark upgrade was the only change in our environment. After taking a look at what
seems to be causing this we noticed that Kryo Serializer is the main culprit for the raise
in memory consumption.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message