Bug #9388
Updated by Peter Amstutz almost 8 years ago
I observed websockets failing to send events that it clearly should have sent.
The issue is with how websockets is querying the database. It assumes monotonically increasing "id" fields.
While "id" is monotonically increasing, the "id" seems to be allocated at the start of record creation, not the end. So a log id '2' could show up before log id '1', if '2' commits before '1'.
The proposed fix is to perform an additional query which checks that there are no gaps in the 'id' sequence. If a gap is found, don't process any events after the gap until it is filled.