carbon-coordination
carbon-coordination copied to clipboard
Events can be missed in high concurrent scenarios
RDBMS coordination read notifications from MEMBERSHIP_EVENT_TABL. After selecting notifications, those are deleted by the destined node. This would lead delete unread notifications in a high concurrent scenario.
The fix is select notifications with event id and then delete notifications by event id.
Related JIRA: https://wso2.org/jira/browse/MB-1881