Publish event for transfers earlier
What does this MR do and why?
Publish event for transfers earlier
The transfer service could timeout after the transaction. This timeout leads to the GroupTransferedEvent not being emitted.
This leads into a semi-atomic transfer operation, because we have listeners on this events and we rely on it being triggered.
Ideally all other (long-running) data migrations should only be handled in workers, instead of the TransferService directly.
To mitigate the problem for now, we publish the GroupTransferedEvent immediately after updating the namespaces.
Changelog: fixed
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Nicolas Dular