You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On other hand, we use another script to continuously kill the pod with warm shutdown, every time a worker pod is kill, another worker pod will be spawned. As I see, when warm shutdown a worker, not-executed tasks will be restored to the queue, and when new worker is spawned, it received the said tasks.
Expected results
200 tasks will be executed
Current result
We tested 2 times.
First round, because the test got stopped by another thread, only 187 tasks are sent and received by celery, only 185 tasks got executed.
Second round, 200 tasks are received, only 198 executed.
Conclusion
There are 1% rate that a tasks will be lost during a warm shutdown.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Test scenario
We use kubernetes to deploy the worker with specific queue name
smart-parking
.We use this loop to continuously send 200 tasks to this queue
On other hand, we use another script to continuously kill the pod with warm shutdown, every time a worker pod is kill, another worker pod will be spawned. As I see, when warm shutdown a worker, not-executed tasks will be restored to the queue, and when new worker is spawned, it received the said tasks.
Expected results
200 tasks will be executed
Current result
We tested 2 times.
First round, because the test got stopped by another thread, only 187 tasks are sent and received by celery, only 185 tasks got executed.
Second round, 200 tasks are received, only 198 executed.
Conclusion
There are 1% rate that a tasks will be lost during a warm shutdown.
Beta Was this translation helpful? Give feedback.
All reactions