-
Notifications
You must be signed in to change notification settings - Fork 129
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
reader: don't send RDY 1 on a new connection if that would violate max-in-flight #254
Merged
mreiferson
merged 4 commits into
nsqio:master
from
alpaker:respect-max-in-flight-on-startup
Oct 24, 2021
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
24a84c2
reader: Don't send RDY 1 on a new connection if that would violate th…
88b5c59
reader: Avoid max-in-flight violations when exiting backoff.
df9ffcc
reader: Avoid max-in-flight violations when dynamically setting max-i…
16abeb7
tests: Add RDY redistribution tests.
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
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.
Should this block instead just set RDY 0 for all connections and let the rest of the logic below identify conns to receive non-zero ready?
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.
With the current redistribution logic I think that change could make it unsafe to call
set_max_in_flight()
with messages in flight. Right now redistribution avoids giving positive RDY to a connection with a message in flight, so something like the following could happen:len(conns)
.c
, reduce m-i-f but keep it >=len(conns)
._redistribute_rdy_state()
sets RDY 0 on all connections, includingc
.c
has something in flight, this redistribution round leavesc
at RDY 0.len(conns)
and so don't redistribute RDY, leavingc
starved.We could make the simplification you suggest if we allow redistribution to give RDY to a conn with something in flight:
which (I think) is fine from a correctness standpoint and will at worst increase the variance in how long it takes to service all connections equally.