-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comment out all references to 'run' queue #3
Comments
Commented out 'run' queue function in sql_client.py and the line that adds to the 'run' queue from worker.py Thinking of keeping this issue open though so that it can potentially get addressed in the future |
Future work: Better understand Cloud SQL to see how much of a 'delay' we can expect before a second sql-client instance can read the point added by the first sql-client instance. From that, decide whether we can re-add the 'run' queue functionality or if it has to be tossed completely. Problem: |
I created a new issue (#6) for fixing 'run' client since this current issue is more about removing all 'run' client references |
GoogleCloudWorker/sql_client.py
Line 267 in 3a0979d
comment out any code dealing with the 'run' queue
Couldn't get the sql server to update quickly enough after one sql client adds a new point so that another sql client can change the state from 'queue' to 'running' after a worker picks it off the 'main' queue...couldn't invest enough time to resolve this issue so commenting out functionality
The text was updated successfully, but these errors were encountered: