cancel
Showing results for 
Search instead for 
Did you mean: 
Warehousing & Analytics
Engage in discussions on data warehousing, analytics, and BI solutions within the Databricks Community. Share insights, tips, and best practices for leveraging data for informed decision-making.
cancel
Showing results for 
Search instead for 
Did you mean: 

Intermittent SQL Failure on Databricks SQL Warehouse

Ramakrishnan83
New Contributor III

Team,

I did setup a SQL Warehouse Cluster to support request from Mobile devices through REST API. I read through the documentation of concurrent query limit which is 10. But in my scenario I had 5 small clusters and the query monitoring indicated there is not peak load or query being queued. But however the front end initiate 2 queries at the same time to 2 different tables(Select query). No complex joins or transformation in the select statement.  These 2 queries gets executed most the of the time in less than a second. But there are scenarios where only one query completes in average of 10-11 seconds and the second query stays in the "Executing" phase and gets time out after 120 seconds. 

The same query gets completed next time if the request comes in. So it is not about the query or data. I am not able to track out why the query fails as the query monitor is also not having much information. 

I would like to understand: 

1. Does databricks SQL Support concurrent read request ? if yes, what is definition of concurrency?

10 read request hitting at the same second/millisecond or max 10 request is processed by the cluster.

2. Does Databricks SQL has logging to trace back the request from the time it hit the SQL Warehouse to completion?

 

1 REPLY 1

198270
New Contributor II

We have a similar problem: our self service BI tool Looker is using SQL warehouse and queries that usually run in a few seconds randomly fail with this message (logged in Looker history explore) "Java::JavaSql::SQLException: [Databricks][JDBCDriver](500580) Operation is canceled.".

We're talking about <1% of queries, but it's still something that we would like to avoid.

My suspicion is also that it is related to concurrency settings of the SQL warehouse.

I couldn't find anything in the docs or in threads about configuring concurrency settings for SQL warehouses.

Can you please help?

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