Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data tests can cause "user query limit" issue if queries queue for over 600 seconds. #671

Closed
DylanBaker opened this issue Dec 22, 2022 · 0 comments · Fixed by #673
Closed
Assignees
Labels
Bug Something isn't working

Comments

@DylanBaker
Copy link
Collaborator

With the recent async changes, we now run all data tests at the same time.

This is from the Looker docs:

Per-user query limit and timeout: To prevent any single user from filling up the Looker query queue, each user has a maximum number of allowed concurrent queries and a corresponding queue timeout. By default, each user can run a maximum of 15 concurrent queries, and the timeout for queries queued due to this limit is 600 seconds.

Some organisaitons have a large number of tests, many of which take a while to run. As a result of this, some organisations are getting errors related to the user query limit when the data test queries take a long time.

I believe the solution is to bound the async tasks with a Semaphore. It probably makes sense to make that number 15, though we could also make it configurable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
2 participants