https://community.databricks.com/t5/administration-architecture/problem-loading-catalog-data-from-multi-node-cluster-after/m-p/68694#M1186 <P><a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/104831">@Flask</a>&nbsp;<BR />As it states in the <A href="https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/vnet-inject" target="_self">documentation</A></P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="daniel_sahal_0-1715320473952.png" style="width: 400px;"><img src="https://community.databricks.com/t5/image/serverpage/image-id/7510i7343D34CF8999612/image-size/medium/is-moderation-mode/true?v=v2&amp;px=400" role="button" title="daniel_sahal_0-1715320473952.png" alt="daniel_sahal_0-1715320473952.png" /></span></P><P>&nbsp;</P> Fri, 10 May 2024 05:55:21 GMT daniel_sahal 2024-05-10T05:55:21Z https://community.databricks.com/t5/administration-architecture/problem-loading-catalog-data-from-multi-node-cluster-after/m-p/68684#M1185 <P>We've changed address range for Vnet and subnet that the Azure Databricks workspace(standard sku) was using, after that when we try to access the catalog data, we're getting <EM>socket closed</EM> error. This error is only with Multi node cluster, for single node it is working fine. Wondering on how to troubleshoot this issue?</P> Fri, 10 May 2024 02:17:15 GMT https://community.databricks.com/t5/administration-architecture/problem-loading-catalog-data-from-multi-node-cluster-after/m-p/68684#M1185 Flask 2024-05-10T02:17:15Z https://community.databricks.com/t5/administration-architecture/problem-loading-catalog-data-from-multi-node-cluster-after/m-p/68694#M1186 <P><a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/104831">@Flask</a>&nbsp;<BR />As it states in the <A href="https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/vnet-inject" target="_self">documentation</A></P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="daniel_sahal_0-1715320473952.png" style="width: 400px;"><img src="https://community.databricks.com/t5/image/serverpage/image-id/7510i7343D34CF8999612/image-size/medium/is-moderation-mode/true?v=v2&amp;px=400" role="button" title="daniel_sahal_0-1715320473952.png" alt="daniel_sahal_0-1715320473952.png" /></span></P><P>&nbsp;</P> Fri, 10 May 2024 05:55:21 GMT https://community.databricks.com/t5/administration-architecture/problem-loading-catalog-data-from-multi-node-cluster-after/m-p/68694#M1186 daniel_sahal 2024-05-10T05:55:21Z https://community.databricks.com/t5/administration-architecture/problem-loading-catalog-data-from-multi-node-cluster-after/m-p/68698#M1187 <P>Yes, it is mentioned that we cannot change the Vnet. I've changed the range in the same vnet but not the Vnet. Is there any troubleshooting that I can do to find this issue. The problem is, I don't want to recreate the workspace. It is a worst case scenario for me and want to explore all the possibilities first.</P> Fri, 10 May 2024 07:09:10 GMT https://community.databricks.com/t5/administration-architecture/problem-loading-catalog-data-from-multi-node-cluster-after/m-p/68698#M1187 Flask 2024-05-10T07:09:10Z