-
Notifications
You must be signed in to change notification settings - Fork 136
app/vlselect: expose the VL-Partial-Response HTTP header
#1438
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
Open
vadimalekseev
wants to merge
1
commit into
master
Choose a base branch
from
partial-response-header
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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 hidden or 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.
This read may race with atomic writes to
qs.QueryCompleteness. Adding a method such as QueryStats.GetQueryCompleteness(), which usesatomic.LoadUint32(), and use it here?Uh oh!
There was an error while loading. Please reload this page.
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.
Initially, there was such a method, but I removed it to simplify the code, because:
writeResponseHeadershere:VictoriaLogs/app/vlstorage/netselect/netselect.go
Line 199 in 3622e0a
VictoriaLogs/app/vlstorage/netselect/netselect.go
Line 136 in 3622e0a
Should we explicitly sync this, do you think?
Uh oh!
There was an error while loading. Please reload this page.
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.
Yeah, I double-checked the code, and the fact that it doesn't need synchronization is really counter-intuitive. I will add explicit synchronizationSee the comment bellow.
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.
Even though this counter-intuitive behavior is basically the core of the whole PR: we cant let another goroutine write
QueryCompletenessComplete, otherwise we'll set the partial response to 'false' for a streaming request.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.
More explicit (but complex) implementation described here: #718 (comment)
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.
Sorry I don't understand, I don't mean waiting until all goroutines finish before writing the header. I mean using atomic load for reading
QueryCompleteness, since the field is updated via atomic/CAS elsewhere. This doesn't change the timing. Could you explain more?Uh oh!
There was an error while loading. Please reload this page.
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.
Hey @func25, I've updated the
runQueryfunction, soQueryStatsupdates only after thewg.Done(). Could you please check again?Previously, there actually could have been a race condition if an empty response was received from vlstorage. In that case, we would never have called
writeBlock, which used to act as a mutex due towriteResponseHeadersOnce.This could lead to a situation where one vlstorage returned an empty response, while the second one was unavailable. In this case, we could potentially set
QueryCompletenessCompleteinstead of Partial. The current code should avoid this situation.