diff options
| author | ijon <ijon@ydb.tech> | 2025-02-05 18:09:01 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-05 18:09:01 +0300 |
| commit | 6cd0f50b87515eba2db841a4a74a7834f6aac684 (patch) | |
| tree | cf697722ebca07e73b8a7a030e05d8fae8d8bc70 /contrib/python/matplotlib/py3/src/array.h | |
| parent | e76be64969996c6c4920b0795e3aa6c772be595b (diff) | |
| download | ydb-6cd0f50b87515eba2db841a4a74a7834f6aac684.tar.gz | |
feature flags: enable EnableAlterDatabaseCreateHiveFirst (#14078)
This is a long awaited improvement in the dedicated database creation process.
`EnableAlterDatabaseCreateHiveFirst` (`enable_alter_database_create_hive_first` in the config) feature flag affects how system tablets of the dedicated database are created (and than managed throughout their lifetime). System tablets (schemeshard, hive, coordinators/mediators, sysview-processor etc) are those that constitute and service the database itself.
Without `EnableAlterDatabaseCreateHiveFirst`, creation of the new dedicated database leaves all it's system tablets in the custody of the main ("root") Hive of the cluster (all other tablets created afterwards live in the custody of the tenant Hive). Database with that separation of responsibilities works fine. The downside is that complete lack of common vision and coordination between two Hives (root and the tenant's) can lead to suboptimal results when database' tablets (both system and others) are balanced under the load.
With `EnableAlterDatabaseCreateHiveFirst`, creation of the new dedicated database leaves all tenant tablets (except tenant Hive) in the custody of the tenant hive. Which alleviates problem with tablet balancing.
Diffstat (limited to 'contrib/python/matplotlib/py3/src/array.h')
0 files changed, 0 insertions, 0 deletions