nsqd: msg_timeout for clients pre 0.2.28 #428
Merged
Conversation
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
|
Yea, this is a bug, Thanks! |
mreiferson
changed the title
|
ping #364 |
|
RFR @jehiah |
jehiah
added a commit
that referenced
this pull request
Jul 30, 2014
nsqd: msg_timeout for clients pre 0.2.28
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
NSQ clients that do not send
msg_timeoutparameter as part ofIDENTIFYget defaulted to the value 0. That value gets sent back to the client and obviously has some odd behavior. It seems like it should be defaulting to 60s which is the configured default.