-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Enhancement] reduce tablet shard read lock holding time when calc persistent index compact score #38299
[Enhancement] reduce tablet shard read lock holding time when calc persistent index compact score #38299
Access has been restricted
You have triggered a rate limit.
Please wait a few minutes before you try again;
in some cases this may take up to an hour.
Conversation
…rsistent index compact score Signed-off-by: luohaha <18810541851@163.com>
47c1831
to
e782047
Compare
[FE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
[BE Incremental Coverage Report]❌ fail : 0 / 10 (00.00%) file detail
|
@Mergifyio backport branch-3.2 |
@Mergifyio backport branch-3.1 |
@Mergifyio backport branch-3.0 |
@Mergifyio backport branch-2.5 |
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
_update_manager->get_pindex_compaction_mgr()->schedule([&]() { | ||
return StorageEngine::instance()->tablet_manager()->pick_tablets_to_do_pk_index_major_compaction(); | ||
}); | ||
if (config::enable_pindex_minor_compaction) { |
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.
why control major compact by minor switch ?
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.
Because if there is no minor compaction, we don't need to do major compaction.
Why I'm doing:
When calc persistent index compact score, if pindex not exist in index cache, we will read persistent meta from rocksdb which can be very slow. We should't hold tablet shard read lock to do this, because it will affect tablet create and drop.
What I'm doing:
Remove persistent index compact score calculation from tablet shard read lock.
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: