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
Add support to flush multiple CFs atomically #4262
Add support to flush multiple CFs atomically #4262
Changes from 5 commits
6c278e9
136bb10
dd8e664
19e5501
32f8c50
3884b80
70e538a
c834396
45a9f5c
a311d59
5691a73
0a138df
f987492
97e5123
ca961e7
2b69378
4144f2b
5e774cb
a003137
51c8ccd
036afce
477ddfa
4cf4872
348553a
411d6ae
c23a1df
6c0e51f
e3e9f7a
06e566f
8d7b8cc
3ae9f54
8a2daf2
893c0da
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.
When would there be zero column families?
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 for the typo. It should be
>1
according to https://github.com/facebook/rocksdb/blob/master/db/db_impl_compaction_flush.cc#L147.Then it means there is possible unnecessary log syncing. I'll submit a separate PR to see if it's indeed the case.
Update
#4416 tries to address this issue, and this PR will remove this check.
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 lost here. Are we still holding DB mutex here?
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.
Yes.
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.
IMO it looks fine since the calls doing I/O (like
SyncClosedLogs
) look like they all release/reacquire the lock.