-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Receive: fix serverAsClient.Series goroutines leak #6948
Merged
GiedriusS
merged 6 commits into
thanos-io:main
from
thibaultmg:fix_goroutines_leak_series_req
May 20, 2024
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
b47865f
fix serverAsClient goroutines leak
thibaultmg f2c0683
fix lint
thibaultmg 6aed256
update changelog
thibaultmg af47f03
delete invalid comment
thibaultmg f75b167
remove temp dev test
thibaultmg 64f38ec
remove timer channel drain
thibaultmg 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
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
Oops, something went wrong.
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.
Could this lead to problems if
s.srv.err
is closed while we are continuously callingRecv()
and there's something to read froms.srv.recv
? In other words, from my understandingselect{}
chooses randomly if there are multiple possibilities so withs.srv.err
closed we could prematurely returnio.EOF
, no? (https://go.dev/ref/spec#Select_statements, see second point). I think the same applies to thecase r, ok
branch. My suggestion would be to give a priority tos.srv.recv
.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 don't think that the race scenario you describe can happen here:
s.srv.err
channel can only be closed whens.srv.Series(in, inSrv)
returns.Series()
method only returns after it has finished pushing data into the unbuffereds.srv.recv
channel.Series()
only returns once the last bits of data have been consumed by theRecv()
caller.Regarding the proposed change to give priority to
s.srv.recv
, I see a potential issue if theSeries()
call returns an error:Recv()
will block on readings.srv.recv
which is not yet closed.Series()
will block trying to write the error into the unbufferederr
channel.WDYT @GiedriusS ?