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
Active changes feeds not notified when deferred sequences get cached #2626
Comments
Possibly related to #2358 |
adamcfraser
pushed a commit
that referenced
this issue
Jun 12, 2017
* Notes from call w/ Adam * Notes on container/heap usage * Fixes #2626 processEntry calls can skip notification when it unblocks pending sequences
jamesnocentini
changed the title
processEntry calls can skip notification when it unblocks pending sequences
Possibility of notifications being skipped which can result in sequence numbers to be wrongly allocated
Jun 15, 2017
adamcfraser
changed the title
Possibility of notifications being skipped which can result in sequence numbers to be wrongly allocated
Active changes feeds not notified when deferred sequences are cached
Jun 15, 2017
adamcfraser
changed the title
Active changes feeds not notified when deferred sequences are cached
Active changes feeds not notified when deferred sequences get cached
Jun 15, 2017
tleyden
added a commit
that referenced
this issue
Jul 28, 2017
* Notes from call w/ Adam * Notes on container/heap usage * Fixes #2626 processEntry calls can skip notification when it unblocks pending sequences # Conflicts: # db/change_cache.go
adamcfraser
pushed a commit
that referenced
this issue
Jul 28, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are several places in change_cache.go where we call processEntry for non-document updates (skipped sequence handling, unused sequence handling, recent sequence handling), and we're not doing listener notification based on the results of that call. The non-document update doesn't require notification, but it's possible that the processEntry call unblocked some pending sequences that DO require notification.
Need to ensure notification happens when a non-empty list of channels is returned from processEntry, in all situations.
The text was updated successfully, but these errors were encountered: