<?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>article When deploying a serverless model, we get &amp;quot;Signal 9&amp;quot; when using small/medium clusters or &amp;quot;Workspace quota exhausted&amp;quot; when using large clusters. in Support FAQs</title>
    <link>https://community.databricks.com/t5/support-faqs/when-deploying-a-serverless-model-we-get-quot-signal-9-quot-when/ta-p/56688</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;Identifying the root cause of worker termination involves analyzing signals that can provide insights into the issue. Typically, these problems are associated with memory pressure, but understanding the specific events, workload type, and workload size is crucial for decoding the underlying problem.&lt;/P&gt;
&lt;P&gt;A&amp;nbsp;&lt;FONT face="courier new,courier"&gt;Workspace quota exhausted&lt;/FONT&gt;&amp;nbsp;error message indicates that the default limit for provisioned concurrency has reached the maximum value of 200. This limit is determined by the highest number of concurrent requests that can be allocated across your endpoints. If an endpoint serves a model with a large size workload, supporting 16-64 concurrent requests, the maximum provisioned concurrency for that endpoint is 64. The cumulative default limit across all endpoints is 200.&lt;/P&gt;
&lt;P&gt;If you need to extend this default limit, contact Databricks support for further assistance.&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Thu, 11 Jan 2024 01:00:00 GMT</pubDate>
    <dc:creator>Adam_Pavlacka</dc:creator>
    <dc:date>2024-01-11T01:00:00Z</dc:date>
    <item>
      <title>When deploying a serverless model, we get "Signal 9" when using small/medium clusters or "Workspace quota exhausted" when using large clusters.</title>
      <link>https://community.databricks.com/t5/support-faqs/when-deploying-a-serverless-model-we-get-quot-signal-9-quot-when/ta-p/56688</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;Identifying the root cause of worker termination involves analyzing signals that can provide insights into the issue. Typically, these problems are associated with memory pressure, but understanding the specific events, workload type, and workload size is crucial for decoding the underlying problem.&lt;/P&gt;
&lt;P&gt;A&amp;nbsp;&lt;FONT face="courier new,courier"&gt;Workspace quota exhausted&lt;/FONT&gt;&amp;nbsp;error message indicates that the default limit for provisioned concurrency has reached the maximum value of 200. This limit is determined by the highest number of concurrent requests that can be allocated across your endpoints. If an endpoint serves a model with a large size workload, supporting 16-64 concurrent requests, the maximum provisioned concurrency for that endpoint is 64. The cumulative default limit across all endpoints is 200.&lt;/P&gt;
&lt;P&gt;If you need to extend this default limit, contact Databricks support for further assistance.&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 11 Jan 2024 01:00:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/support-faqs/when-deploying-a-serverless-model-we-get-quot-signal-9-quot-when/ta-p/56688</guid>
      <dc:creator>Adam_Pavlacka</dc:creator>
      <dc:date>2024-01-11T01:00:00Z</dc:date>
    </item>
  </channel>
</rss>

