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
I have setup a queue to perform the conversions. I found a bug when the 'perform_conversions' and 'generate_responsive_images' jobs run on different workers. The data saved to the database in 'perform_conversions' and 'generate_responsive_images' will overlap if these 2 jobs run simultaneously on 2 workers. I think these 2 jobs should be extended with Laravel Atomic Locks.
Currently, to fix this bug, I only run the jobs on one queue and have only 1 worker listen to that queue.
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
-
I have setup a queue to perform the conversions. I found a bug when the 'perform_conversions' and 'generate_responsive_images' jobs run on different workers. The data saved to the database in 'perform_conversions' and 'generate_responsive_images' will overlap if these 2 jobs run simultaneously on 2 workers. I think these 2 jobs should be extended with Laravel Atomic Locks.
Currently, to fix this bug, I only run the jobs on one queue and have only 1 worker listen to that queue.
Beta Was this translation helpful? Give feedback.
All reactions