Delay user storage cluster sync event to after completion#48697
Delay user storage cluster sync event to after completion#48697pedroigor wants to merge 1 commit intokeycloak:mainfrom
Conversation
Closes keycloak#48666 Signed-off-by: Pedro Igor <pigor.craveiro@gmail.com>
ahus1
left a comment
There was a problem hiding this comment.
Thank you for the change. I think it is incomplete, and this is probably also the reason why reading the information on a second node is incomplete.
The current event notification is wrapped inside a new transaction. So when the inner transaction ends, the outer transaction hasn't yet written the information the database.
I suppose that in the following snippet, the runJobInTransaction() needs to be removed to make this work as expected.
The snippet above was added in commit 5e3c0b6 which might need a different solution. That commit updates some enlisteAfterCompletion blocks for removeRealm() and importRealm(). Those might no longer be necessary as those events are now delivered after the commit to the database has taken place.
|
@ahus1 Do you mean in order to fix the behavior when propagating the full user storage provider model within the cluster event? |
Closes #48666