-
Notifications
You must be signed in to change notification settings - Fork 606
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
24-3: schemeshard: fix crash on concurrent alter-extsubdomains #9201
24-3: schemeshard: fix crash on concurrent alter-extsubdomains #9201
Conversation
…db-platform#9157) KIKIMR-21965 Enforce creation of `TAlterExtSubDomain` operations only through `CreateCompatibleAlterExtSubDomain()` to ensure all proper state checking. ### Changelog category * Not for changelog
…ubDomain TAlterExtSubDomain suboperation should be able accept ESchemeOpAlterSubDomain operation type. This is special compatibility case for those old subdomains that went through migration to a separate tenants at some time. Console tablet holds records about types of the subdomains but they hadn't been updated at the time of migration. So Console still thinks that old subdomains are plain subdomains whereas they had been migrated to the extsubdomains. And Console tablet is the main source of the subdomains alters. This compatibility case should be upholded until Console records will be fixed. KIKIMR-21965
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
merge 5c36245(#9157), ...(#9198) from
main
KIKIMR-21965
TAlterExtSubDomain
operations only throughCreateCompatibleAlterExtSubDomain()
to ensure all proper state checkingTAlterExtSubDomain
compatibility with ESchemeOpAlterSubDomainChangelog category