-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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(tsi1): fix data race between appendEntry and FlushAndSync tsi1.(*LogFile) #25182
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
davidby-influx
approved these changes
Jul 23, 2024
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.
LGTM. Thank you for your contribution!
gwossum
reviewed
Jul 23, 2024
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.
Looks good to me, too. Thanks!
chengshiwen
added a commit
to chengshiwen/influxdb
that referenced
this pull request
Aug 11, 2024
…LogFile) (influxdata#25182) Extend lock lifespan to encompass the flushAndSync() call to avoid a race closes influxdata#25181
davidby-influx
pushed a commit
that referenced
this pull request
Aug 12, 2024
chengshiwen
added a commit
to chengshiwen/influxdb
that referenced
this pull request
Aug 27, 2024
…LogFile) (influxdata#25182) Extend lock lifespan to encompass the flushAndSync() call to avoid a race closes influxdata#25181
chengshiwen
added a commit
to chengshiwen/influxdb
that referenced
this pull request
Aug 28, 2024
…LogFile) (influxdata#25182) Extend lock lifespan to encompass the flushAndSync() call to avoid a race closes influxdata#25181
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.
Closes #25181
Describe your proposed changes here.
From version 1.6.6 to 1.8.10, there are two relevant changes in
tsdb/index/tsi1/log_file.go
:f.mu.RLock()
has been used instead off.mu.Lock()
inWrites(entries []LogEntry)
, causing an internal map to be modified for concurrent useExecEntries
andf.FlushAndSync
So this pull request first reverts 4ef4fe9, and then changes
f.mu.RLock()
tof.mu.Lock()
.Then this issue did not recur.
@davidby-influx