<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Spark out of memory error.You can resolve this error by increasing the size of cluster in Databricks. in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19859#M13386</link>
    <description>&lt;P&gt;@S S​&amp;nbsp;every time cluster increase may not be good solution, based on scenarios it gets changed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;sometimes we may need to tweak code &lt;/LI&gt;&lt;LI&gt;sometimes we may need to add memory parameters&lt;/LI&gt;&lt;LI&gt;Based on ganglia metrics we can get more information   &lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Tue, 29 Nov 2022 21:11:55 GMT</pubDate>
    <dc:creator>karthik_p</dc:creator>
    <dc:date>2022-11-29T21:11:55Z</dc:date>
    <item>
      <title>Spark out of memory error.You can resolve this error by increasing the size of cluster in Databricks.</title>
      <link>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19858#M13385</link>
      <description>&lt;P&gt;Spark out of memory error.&lt;/P&gt;&lt;P&gt;You can resolve this error by increasing the size of cluster in Databricks.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 20:08:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19858#M13385</guid>
      <dc:creator>SS2</dc:creator>
      <dc:date>2022-11-29T20:08:49Z</dc:date>
    </item>
    <item>
      <title>Re: Spark out of memory error.You can resolve this error by increasing the size of cluster in Databricks.</title>
      <link>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19859#M13386</link>
      <description>&lt;P&gt;@S S​&amp;nbsp;every time cluster increase may not be good solution, based on scenarios it gets changed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;sometimes we may need to tweak code &lt;/LI&gt;&lt;LI&gt;sometimes we may need to add memory parameters&lt;/LI&gt;&lt;LI&gt;Based on ganglia metrics we can get more information   &lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Tue, 29 Nov 2022 21:11:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19859#M13386</guid>
      <dc:creator>karthik_p</dc:creator>
      <dc:date>2022-11-29T21:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: Spark out of memory error.You can resolve this error by increasing the size of cluster in Databricks.</title>
      <link>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19860#M13387</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agree​, it is better if you improve you code rather than increase the size of cluster. You can config the number of partitions. &lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 04:00:07 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19860#M13387</guid>
      <dc:creator>NhatHoang</dc:creator>
      <dc:date>2022-11-30T04:00:07Z</dc:date>
    </item>
    <item>
      <title>Re: Spark out of memory error.You can resolve this error by increasing the size of cluster in Databricks.</title>
      <link>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19861#M13388</link>
      <description>&lt;P&gt;Directly jumping on solution to inc the cluster size is not advisible. I found this nicely written blog what could be potential reason and some initial steps to resolve the OOM error in spark.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://medium.com/swlh/spark-oom-error-closeup-462c7a01709d" alt="https://medium.com/swlh/spark-oom-error-closeup-462c7a01709d" target="_blank"&gt;https://medium.com/swlh/spark-oom-error-closeup-462c7a01709d&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 06:41:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19861#M13388</guid>
      <dc:creator>Shalabh007</dc:creator>
      <dc:date>2022-11-30T06:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: Spark out of memory error.You can resolve this error by increasing the size of cluster in Databricks.</title>
      <link>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19862#M13389</link>
      <description>&lt;P&gt;Adding some more points to @karthik p​&amp;nbsp;'s answer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Use kryo serializer instead of java serializer.&lt;/LI&gt;&lt;LI&gt;Use an optimised garbage collector such as G1GC.&lt;/LI&gt;&lt;LI&gt;Use partitioning wisely on a field.&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 30 Nov 2022 10:00:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/spark-out-of-memory-error-you-can-resolve-this-error-by/m-p/19862#M13389</guid>
      <dc:creator>DK03</dc:creator>
      <dc:date>2022-11-30T10:00:27Z</dc:date>
    </item>
  </channel>
</rss>

