-
Notifications
You must be signed in to change notification settings - Fork 5.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
Support dynamic change to DDL job configuration #57229
Labels
type/feature-request
Categorizes issue or PR as related to a new feature.
Comments
tangenta
added
the
type/feature-request
Categorizes issue or PR as related to a new feature.
label
Nov 8, 2024
This was referenced Nov 11, 2024
13 tasks
This was referenced Nov 14, 2024
13 tasks
This was referenced Nov 19, 2024
ti-chi-bot
pushed a commit
to ti-chi-bot/tidb
that referenced
this issue
Nov 21, 2024
13 tasks
Merged
13 tasks
13 tasks
This was referenced Nov 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Is your feature request related to a problem? Please describe:
TiDB v8.3.0 removes the dynamic change feature for
tidb_ddl_reorg_worker_cnt
andtidb_ddl_reorg_batch_size
, but this feature is useful in some scenarios:The foreseeable business peak arrives during the DDL operation, and it is necessary to reduce DDL's impact on the cluster.
Although the above scenario can be bypassed by canceling and re-executing DDL, it reduces usability and affects user experience.
Describe the feature you'd like:
Add a new syntax that supports dynamically changing relevant config for DDL jobs.
This syntax refers to the ADMIN clause currently supported by TiDB.
THREAD
andBATCH_SIZE
only work for DDLs that need to reorganize data (reorg) types, currently includingADD INDEX
,MODIFY COLUMN
, andREORGANIZE PARTITION
. Changing job config is not supported for non-reorg DDLs.On the other hand, add a column
COMMENTS
to the result set ofADMIN SHOW DDL JOBS
, which displays the current DDL job config:Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
The text was updated successfully, but these errors were encountered: