yugabyte/yugabyte-db

[DocDB] DROP DATABASE ChangeMetaDataOperation performance optimization

Open

#14,786 opened on Nov 1, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (1,003 forks)batch import
area/docdbgood first issuekind/enhancementpriority/medium

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-4104

Description

CatalogManager::DeleteYsqlDBTables currently calls sys_catalog_->DeleteYsqlSystemTable() for each table to be deleted. This results in a SyncReplicateChangeMetadataOperation() for each table. We could follow what we did for CREATE DATABASE in CatalogManager::CopyPgsqlSysTables to batch all those operations into one.

Contributor guide

Research direction
Study the batch implementation used in CatalogManager::CopyPgsqlSysTables for CREATE DATABASE and apply a similar approach to CatalogManager::DeleteYsqlDBTables for DROP DATABASE, specifically batching SyncReplicateChangeMetadataOperation calls into one.
Tech stack
cppsql
Domain
databasebackend
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50