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.
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
fix concurrency issue #22
base: master
Are you sure you want to change the base?
fix concurrency issue #22
Changes from 1 commit
2516d10
94d0c84
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I'm in too minds if we want to do this, it adds the lock overhead to a client which can only perform one request at a time. This falls under the remit of nothing being concurrent safe unless documented to be so.
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.
I can try to think of a better solution to solve this but it should definitely be concurrent safe imho (the fact that two people reported the issue suggests that it's expected despite not being "documented to be so").
Is the tiny overhead really that significant in this use case?
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.
My issue doesn't come from trying to use the library from multiple goroutines at once.
My issue happens once unhandled timeout/connection closed errors occur. (for example:
read: connection reset by peer
)Because the next time I execute a command on that closed connection, the
conn.Write()
call freezes indefinitely, causing the issue.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.
enabling keepalive on the connection should fix this
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.
conn.Write()
should also never freeze "indefinitely", only as long as the Timeout that is specified/DefaultTimout
, since there's a Deadline set before calling it.