cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

select 1 query not finishing

Bepposbeste1993
New Contributor III

Hello,

I have the issue that even a query like "select 1" is not finishing. The sql warehouse runs infinite. I have no idea where to look for any issues because in the SPARK UI I cant see any error.

What is intresting is that also allpurpose clusters (multi node) are also affected

%sql
select 1

wont finish.

If I choose a single node cluster the thing is finishing within 2 seconds. 

Any help would be appreciated that leads to the solution

1 ACCEPTED SOLUTION

Accepted Solutions

Bepposbeste1993
New Contributor III

We solved the issue with MSFT and Databricks Support.

So our infrastructure was VNET injected. Technically it is possible to change the subnet size eventhough its not supported according to documentation. 

The result is then a randomized behaviour depending where Databricks puts the nodes "on the subnet". If its on the old range - all is fine and if its on the new range, you get the above mentioned behaviour.

Changing the subnet range back solved our issue.

View solution in original post

3 REPLIES 3

Alberto_Umana
Databricks Employee
Databricks Employee

Hi @Bepposbeste1993,

Have you tried adding the full path to the table you are querying? catalog.schema.table?

Additionally when using multi node do you have any special spark setting? You can validate cluster driver logs under log4j to validate if any errors during query executing to obtain more details on the behavior.

Bepposbeste1993
New Contributor III

We solved the issue with MSFT and Databricks Support.

So our infrastructure was VNET injected. Technically it is possible to change the subnet size eventhough its not supported according to documentation. 

The result is then a randomized behaviour depending where Databricks puts the nodes "on the subnet". If its on the old range - all is fine and if its on the new range, you get the above mentioned behaviour.

Changing the subnet range back solved our issue.

Alberto_Umana
Databricks Employee
Databricks Employee

Hi @Bepposbeste1993,

Do you have the case ID raised for this issue? 

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโ€™t want to miss the chance to attend and share knowledge.

If there isnโ€™t a group near you, start one and help create a community that brings people together.

Request a New Group