<?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: Why driver memory is capped in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/why-driver-memory-is-capped/m-p/91884#M38288</link>
    <description>&lt;P&gt;Could you please try increase the partition the Dataframe&amp;nbsp;by doing repartition() before you merge.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 26 Sep 2024 13:27:58 GMT</pubDate>
    <dc:creator>Kannathasan</dc:creator>
    <dc:date>2024-09-26T13:27:58Z</dc:date>
    <item>
      <title>Why driver memory is capped</title>
      <link>https://community.databricks.com/t5/data-engineering/why-driver-memory-is-capped/m-p/91812#M38270</link>
      <description>&lt;P&gt;Hi team&lt;/P&gt;&lt;P&gt;We are using a job cluster to run spark with MERGE. Somehow it needs a lot driver memory. We allocate 128G+16core node for driver, and specify spark.driver.memory=96000m. We can see it is 96000m from env table of spark UI. The config is like:&lt;/P&gt;&lt;P&gt;"spark.driver.memory": "96000m",&lt;BR /&gt;"spark.memory.offHeap.size": "11872m",&lt;BR /&gt;"spark.executor.memory": "86000m",&lt;/P&gt;&lt;P&gt;however from metrics of the cluster, the driver memory is capped below 48G. How to make driver to fully use the memory?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 06:37:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-driver-memory-is-capped/m-p/91812#M38270</guid>
      <dc:creator>MikeGo</dc:creator>
      <dc:date>2024-09-26T06:37:46Z</dc:date>
    </item>
    <item>
      <title>Re: Why driver memory is capped</title>
      <link>https://community.databricks.com/t5/data-engineering/why-driver-memory-is-capped/m-p/91884#M38288</link>
      <description>&lt;P&gt;Could you please try increase the partition the Dataframe&amp;nbsp;by doing repartition() before you merge.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 13:27:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-driver-memory-is-capped/m-p/91884#M38288</guid>
      <dc:creator>Kannathasan</dc:creator>
      <dc:date>2024-09-26T13:27:58Z</dc:date>
    </item>
    <item>
      <title>Re: Why driver memory is capped</title>
      <link>https://community.databricks.com/t5/data-engineering/why-driver-memory-is-capped/m-p/91980#M38308</link>
      <description>&lt;P&gt;Thanks for response. We are doubt why driver memory cannot be fully used (only 48G out of 128G is used for driver). Is this related with repartition?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2024 01:08:02 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-driver-memory-is-capped/m-p/91980#M38308</guid>
      <dc:creator>MikeGo</dc:creator>
      <dc:date>2024-09-27T01:08:02Z</dc:date>
    </item>
  </channel>
</rss>

