<?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: SUBNET_EXHAUSTED_FAILURE(CLOUD_FAILURE):  or No more address space to create NIC within injected virtual network in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/subnet-exhausted-failure-cloud-failure-or-no-more-address-space/m-p/12205#M7054</link>
    <description>&lt;P&gt;Thanks for your answer!! &lt;/P&gt;&lt;P&gt;What all objects will be impacted in data bricks while applying the changes/increasing IPs (Clusters should not be in running status, mount location, etc). so that will take appropriate action before applying the changes.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Jan 2023 07:54:44 GMT</pubDate>
    <dc:creator>Phani1</dc:creator>
    <dc:date>2023-01-13T07:54:44Z</dc:date>
    <item>
      <title>SUBNET_EXHAUSTED_FAILURE(CLOUD_FAILURE):  or No more address space to create NIC within injected virtual network</title>
      <link>https://community.databricks.com/t5/data-engineering/subnet-exhausted-failure-cloud-failure-or-no-more-address-space/m-p/12203#M7052</link>
      <description>&lt;P&gt;Currently we are using an all-purpose compute cluster. When we tried to allocate the scheduled jobs to job cluster, we are blocked at the following error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;SUBNET_EXHAUSTED_FAILURE(CLOUD_FAILURE): &lt;/B&gt;azure_error_code:SubnetIsFull,azure_error_message:&lt;B&gt;No more address space to create NIC within injected virtual network. Details:&lt;/B&gt; {&amp;nbsp;&amp;nbsp;"error": {&amp;nbsp;&amp;nbsp;&amp;nbsp;"code": "SubnetIsFull",&amp;nbsp;&amp;nbsp;&amp;nbsp;"message": "Subnet public-subnet-databricks-wwmddatabricksnonprod01 with address prefix 10.99.0.0/26 does not have enough capacity for 1 IP addresses.",&amp;nbsp;&amp;nbsp;&amp;nbsp;"details": []&amp;nbsp;&amp;nbsp;} },databricks_error_message:Error code: SubnetIsFull, error message: No more address space to create NIC within injected virtual network. Details: {&amp;nbsp;&amp;nbsp;"error": {&amp;nbsp;&amp;nbsp;&amp;nbsp;"code": "SubnetIsFull",&amp;nbsp;&amp;nbsp;&amp;nbsp;"message": "Subnet public-subnet-databricks-wwmddatabricksnonprod01 with address prefix 10.99.0.0/26 does not have enough capacity for 1 IP addresses.",&amp;nbsp;&amp;nbsp;&amp;nbsp;"details": []&amp;nbsp;&amp;nbsp;} }&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We raised a service request to the cloud vendor, Microsoft recommended updating the CIDR range on the Databricks workspace to allocate more no. of IPs to the Network address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please help us to clarify the below questions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;1)What all are data bricks objects will impact/have to take care of during the updating CIDR range&lt;/B&gt; on the Databricks workspace to allocate more no. of IPs to the Network address space&lt;/P&gt;&lt;P&gt;2)Is it the right approach to what we are doing, or is there any alternate way?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 05:01:19 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/subnet-exhausted-failure-cloud-failure-or-no-more-address-space/m-p/12203#M7052</guid>
      <dc:creator>Phani1</dc:creator>
      <dc:date>2023-01-13T05:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: SUBNET_EXHAUSTED_FAILURE(CLOUD_FAILURE):  or No more address space to create NIC within injected virtual network</title>
      <link>https://community.databricks.com/t5/data-engineering/subnet-exhausted-failure-cloud-failure-or-no-more-address-space/m-p/12204#M7053</link>
      <description>&lt;P&gt;Answering your questions - yes, your vnet/subnet is out of non-occupied IPs and this can be fixed by allocating more IPs to your network address space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each cluster requires it's own IP, so if there are none available, it simply cannot start.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 07:39:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/subnet-exhausted-failure-cloud-failure-or-no-more-address-space/m-p/12204#M7053</guid>
      <dc:creator>daniel_sahal</dc:creator>
      <dc:date>2023-01-13T07:39:41Z</dc:date>
    </item>
    <item>
      <title>Re: SUBNET_EXHAUSTED_FAILURE(CLOUD_FAILURE):  or No more address space to create NIC within injected virtual network</title>
      <link>https://community.databricks.com/t5/data-engineering/subnet-exhausted-failure-cloud-failure-or-no-more-address-space/m-p/12205#M7054</link>
      <description>&lt;P&gt;Thanks for your answer!! &lt;/P&gt;&lt;P&gt;What all objects will be impacted in data bricks while applying the changes/increasing IPs (Clusters should not be in running status, mount location, etc). so that will take appropriate action before applying the changes.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 07:54:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/subnet-exhausted-failure-cloud-failure-or-no-more-address-space/m-p/12205#M7054</guid>
      <dc:creator>Phani1</dc:creator>
      <dc:date>2023-01-13T07:54:44Z</dc:date>
    </item>
  </channel>
</rss>

