-
Notifications
You must be signed in to change notification settings - Fork 25
feat: delay step transition until all media is processed #72
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
Conversation
src/Migration/MessageQueue/Handler/Processor/MediaProcessingProcessor.php
Show resolved
Hide resolved
src/Migration/MessageQueue/Handler/Processor/MediaProcessingProcessor.php
Show resolved
Hide resolved
|
@jozsefdamokos thanks for the PR description 👍 . Some thoughts on these points from my side 😅
Alright, no shame in doing so and it makes things a lot simpler for us to reason about which is better then race condition bugs on customer systems 👍
Taking a step back, does that make sense to you? To me it sounds like we don't need
Also sounds reasonable to me. Did you somehow manage to measure how long the processing of these messages take with that "batch size", ideally downloading from a remote server like a Shopware build (ShopDev) instance? We should just make sure we stay well below the 30s request timeout limit (in case someone migrates with the admin worker instead of proper cli worker). |
|
@MalteJanz Yes, I thought about merging them, I just chose the quicker way for now to validate that this approach works. I agree, we should merge the two now if the approach of moving away from parallel processing is fine. |
8ee96a4 to
1b06549
Compare
MalteJanz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 , only found one more file that can be removed now I think 🙂
fixes: #10822
MediaProcessingProcessornow