Dataset refreshing error :

[woogie]

Hi,

Refresh error keep occur when I try to refresh using refreshing button top of the main bar.

(DataSource.Error: ODBC: ERROR [HY000] [Treasure Data][Presto] (1060) Presto Query Error: Too many queued queries for "username" (131074))

1) PBI has approx. 30 queries. (queries are connected to Database server using with SQL)

2) Parallel load(option) was deactivated.

3) Data refreshing were worked until last week.

4) But it's not working from this week.

5) I'm attaching some images of my setting(option) below

How can I fix this problem? ☹️

Thanks.

[rubayatyasmin]

Hi, @woogie 

The error you're getting seems to indicate that too many queries have been queued for the user "username" on your Presto database server. Here are a few suggestions you might consider:

1. Check for Running Queries: Check if there are any long-running or stuck queries on the Presto server that are hogging up the queue. If there are, terminating them might help resolve the issue.

2. Increase Concurrent Queries Limit: If it's possible and acceptable in your environment, you might want to increase the limit of concurrent queries that your Presto server can handle.

3. Throttle your Queries: If you can't increase the concurrent query limit, consider running fewer queries at a time from Power BI or increasing the intervals between them.

4. Check for Errors in the SQL Statements: If there's an error in your SQL statements that is causing the queries to not complete, then they could be staying in the queue and not freeing up space for new ones. Validate your SQL syntax and make sure they are running as expected.

5. Monitor Presto Cluster: Use the Presto web interface to monitor the state of your cluster and queries. This can give you some insight into what's going on and why the queries are not completing.

6. Check Connection Pooling: If you're using a connection pool, make sure it's properly configured. Too many idle connections might be blocking new ones.

Remember that changing these settings can have a significant impact on your database server, so make sure you thoroughly test any changes in a non-production environment first, and only make changes you're comfortable with and understand.