Move query execution to RQ
See original GitHub issueMove the execute_query
task from Celery to RQ. Once this is done, we’re Celery free. 🎉
Depends on #4305 and ability to cancel jobs (rq/rq#684, which we will probably implement in a custom Worker in our codebase and then try to port to RQ).
(Opening this to track the work, but this is currently sparse on details)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Jobs - Python RQ
Time to live for job in queue ... A job has two TTLs, one for the job result, result_ttl , and one for...
Read more >Module: RQ::Usage — Documentation for rq (3.3.0)
<<-usage_banner NAME rq v#{ VERSION } SYNOPSIS rq (queue | export RQ_Q=q) mode ... list, status, delete, update, query, execute, configure, snapshot, lock, ......
Read more >sql server - Move the constant to variable in the where clause ...
The first query will have a query plan compiled based on the values of your literals 10000 and '1/1/2018' and the histogram statistics...
Read more >Cloud Spanner federated queries | BigQuery
BigQuery Spanner federation enables BigQuery to query data residing in Spanner in real-time, without copying or moving data. Before you begin. Ensure that...
Read more >Query options | CDP Public Cloud - Cloudera Documentation
Time spent planning the query, scheduling the query, or in admission control is not counted towards the execution time limit. SELECT statements are...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I guess we can close this?
I don’t know if it complicates things much, but we should consider having an optional handler function (in the query runner) that does the actual cancel and if it’s not available then resort to current “kill process”.
This will allow for implementing #4410 or MySQL’s cancel procedure without the use of threads.
This is a nice to have of course and if it complicates the implementation let’s move on with implementing the current behavior (of sending an interrupt signal and on second try a kill signal).