This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Improve warning about notifications queue and remove spurious triggers #5512
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5465590
Better logging for notifications and buffer size increase
tomaka 8cc37a6
Address review
tomaka 5fbc87a
Merge remote-tracking branch 'upstream/master' into notifs-queue-change
tomaka 1d93d52
Merge branch 'master' into notifs-queue-change
tomaka 597fb24
Improve warning about notifications queue and remove spurious triggers
tomaka File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In regards to observing even though the message is dropped: If we only
observe
when the message was actually sent, the histogramcount
metric would tell us how many messages went into the channel. Later on we could add an additional metric (a simple counter) to count the messages being dropped. What do you think @tomaka? Would that enable us to deeper understand the behavior?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally fine if you see this more as a hack than a useful feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The way I see it, dropping messages is something that is really not supposed to happen, and knowing how many messages are dropped isn't necessarily useful, as we have to treat 1 dropped message the same as 500 dropped messages.
Additionally #5481 would consist in reworking this code anyway.