Replies: 1 comment
-
FWIW, if I upgrade the worker to 4.4.7 this works correctly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Question about mixing versions.
I'm upgrading my celery work dispatcher.
Previously the dispatcher and workers were running celery 3.1.26.post2.
I'm upgrading the dispatcher to 5.1.2, but not (yet) upgrading the workers.
We have scripts that attempt to report on which workers are busy or available and use that info to see if there are available workers. With the upgraded dispatcher, this is failing. The problem appears to come down to the behavior of app.control Inspect.
Let's say we have one worker, test100.my.com (names are made up). It is idle.
With the 3.1.26 dispatcher the call app.control.inspect().active() returns
{ 'worker@test100.my.com: [] }
But with 5.1.2 the call app.control.inspect().active() returns:
{ 'worker@test100.my.com': {'error': "KeyError(u'active',)"} }
which breaks our scripts.
The call to inspect the explicitly named worker "app.control.inspect(['worker@test100.my.com']).active()" also returns the KeyError.
Should this work across versions?
Beta Was this translation helpful? Give feedback.
All reactions