<?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: Job queue for pool limit in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/job-queue-for-pool-limit/m-p/50837#M28914</link>
    <description>&lt;P&gt;Try increasing your &lt;SPAN&gt;max capacity limit and might want to bring down the min number of nodes the job uses.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At the job level try configuring retry and time interval between retries.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 10 Nov 2023 20:18:41 GMT</pubDate>
    <dc:creator>SSundaram</dc:creator>
    <dc:date>2023-11-10T20:18:41Z</dc:date>
    <item>
      <title>Job queue for pool limit</title>
      <link>https://community.databricks.com/t5/data-engineering/job-queue-for-pool-limit/m-p/50730#M28875</link>
      <description>&lt;P&gt;I have a cluster pool with a max capacity limit, to make sure we're not burning too extra silicon. We use this for some of our less critical workflow/jobs. They still spend a lot of time idle, but sometimes hit this max capacity limit. Is there a way to get a job to wait for an available pool instance, rather than automatically failing with an&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;instance_pool_error_code:INSTANCE_POOL_MAX_CAPACITY_FAILURE&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 10:35:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/job-queue-for-pool-limit/m-p/50730#M28875</guid>
      <dc:creator>andyh</dc:creator>
      <dc:date>2023-11-09T10:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: Job queue for pool limit</title>
      <link>https://community.databricks.com/t5/data-engineering/job-queue-for-pool-limit/m-p/50829#M28908</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/93251"&gt;@andyh&lt;/a&gt;&amp;nbsp;did you get a chance to check queue in jobs, that may help, will update if we have any other options&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 18:33:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/job-queue-for-pool-limit/m-p/50829#M28908</guid>
      <dc:creator>karthik_p</dc:creator>
      <dc:date>2023-11-10T18:33:32Z</dc:date>
    </item>
    <item>
      <title>Re: Job queue for pool limit</title>
      <link>https://community.databricks.com/t5/data-engineering/job-queue-for-pool-limit/m-p/50837#M28914</link>
      <description>&lt;P&gt;Try increasing your &lt;SPAN&gt;max capacity limit and might want to bring down the min number of nodes the job uses.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At the job level try configuring retry and time interval between retries.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 20:18:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/job-queue-for-pool-limit/m-p/50837#M28914</guid>
      <dc:creator>SSundaram</dc:creator>
      <dc:date>2023-11-10T20:18:41Z</dc:date>
    </item>
  </channel>
</rss>

