<?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: How the Scale up process done in the databricks cluster? in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/how-the-scale-up-process-done-in-the-databricks-cluster/m-p/104857#M9451</link>
    <description>&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;Databricks uses autoscaling to manage the number of worker nodes in a cluster based on the workload. When you configure a cluster with a minimum and maximum number of worker nodes, Databricks automatically adjusts the number of workers within this range based on the demand.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;The autoscaling process works as follows:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;&lt;STRONG&gt;Initial Setup&lt;/STRONG&gt;: When you start the cluster, it begins with the minimum number of worker nodes specified (in your case, 1 worker node).&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;STRONG&gt;Scaling Up&lt;/STRONG&gt;: Databricks monitors the workload on the cluster. If the workload increases and the current number of worker nodes is insufficient to handle the load, Databricks will add more worker nodes up to the maximum limit specified (3 worker nodes in your case). The scaling up process is triggered by the demand for resources such as CPU and memory.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;&lt;STRONG&gt;Scaling Down&lt;/STRONG&gt;: Similarly, if the workload decreases and the current number of worker nodes is more than necessary, Databricks will remove worker nodes to save costs, but it will not go below the minimum number of worker nodes specified.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;The specific thresholds and rules for scaling up and down are managed by Databricks' autoscaling algorithms. For example, optimized autoscaling in Databricks can scale up from the minimum to the maximum number of nodes in two steps and can scale down based on the underutilization of nodes over a certain period (e.g., 40 seconds for job compute and 150 seconds for all-purpose compute).&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV class="_1sijkvt3"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;Doc -&amp;nbsp;&lt;A href="https://docs.databricks.com/en/compute/configure.html#how-autoscaling-behaves" target="_blank"&gt;https://docs.databricks.com/en/compute/configure.html#how-autoscaling-behaves&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jan 2025 07:55:49 GMT</pubDate>
    <dc:creator>NandiniN</dc:creator>
    <dc:date>2025-01-09T07:55:49Z</dc:date>
    <item>
      <title>How the Scale up process done in the databricks cluster?</title>
      <link>https://community.databricks.com/t5/get-started-discussions/how-the-scale-up-process-done-in-the-databricks-cluster/m-p/65795#M9449</link>
      <description>&lt;P&gt;For my AWS databricks cluster, i configured shared computer with 1min worker node and 3 max worker node, initailly only one worker node and driver node instance is created in the AWS console.&amp;nbsp;&lt;BR /&gt;Is there any rule set by databricks for scale up the next node like any threshold exceeds in the initial node(min node)?&lt;/P&gt;&lt;P&gt;How the scale up process done from one node to another node by databricks automatically?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2024 10:51:09 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/how-the-scale-up-process-done-in-the-databricks-cluster/m-p/65795#M9449</guid>
      <dc:creator>Nandhini_Kumar</dc:creator>
      <dc:date>2024-04-08T10:51:09Z</dc:date>
    </item>
    <item>
      <title>Re: How the Scale up process done in the databricks cluster?</title>
      <link>https://community.databricks.com/t5/get-started-discussions/how-the-scale-up-process-done-in-the-databricks-cluster/m-p/104857#M9451</link>
      <description>&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;Databricks uses autoscaling to manage the number of worker nodes in a cluster based on the workload. When you configure a cluster with a minimum and maximum number of worker nodes, Databricks automatically adjusts the number of workers within this range based on the demand.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;The autoscaling process works as follows:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;&lt;STRONG&gt;Initial Setup&lt;/STRONG&gt;: When you start the cluster, it begins with the minimum number of worker nodes specified (in your case, 1 worker node).&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;STRONG&gt;Scaling Up&lt;/STRONG&gt;: Databricks monitors the workload on the cluster. If the workload increases and the current number of worker nodes is insufficient to handle the load, Databricks will add more worker nodes up to the maximum limit specified (3 worker nodes in your case). The scaling up process is triggered by the demand for resources such as CPU and memory.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;&lt;STRONG&gt;Scaling Down&lt;/STRONG&gt;: Similarly, if the workload decreases and the current number of worker nodes is more than necessary, Databricks will remove worker nodes to save costs, but it will not go below the minimum number of worker nodes specified.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;The specific thresholds and rules for scaling up and down are managed by Databricks' autoscaling algorithms. For example, optimized autoscaling in Databricks can scale up from the minimum to the maximum number of nodes in two steps and can scale down based on the underutilization of nodes over a certain period (e.g., 40 seconds for job compute and 150 seconds for all-purpose compute).&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV class="_1sijkvt3"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;Doc -&amp;nbsp;&lt;A href="https://docs.databricks.com/en/compute/configure.html#how-autoscaling-behaves" target="_blank"&gt;https://docs.databricks.com/en/compute/configure.html#how-autoscaling-behaves&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jan 2025 07:55:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/how-the-scale-up-process-done-in-the-databricks-cluster/m-p/104857#M9451</guid>
      <dc:creator>NandiniN</dc:creator>
      <dc:date>2025-01-09T07:55:49Z</dc:date>
    </item>
  </channel>
</rss>

