-
Notifications
You must be signed in to change notification settings - Fork 702
Public API bootstrap command #12308
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
Public API bootstrap command #12308
Conversation
⚪ |
845103f
to
9a54e3c
Compare
@@ -10,6 +11,7 @@ TCommandAdmin::TCommandAdmin() | |||
{ | |||
AddCommand(std::make_unique<NDynamicConfig::TCommandConfig>()); | |||
AddCommand(std::make_unique<NDynamicConfig::TCommandVolatileConfig>()); | |||
AddCommand(std::make_unique<NCluster::TCommandCluster>()); |
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.
Aren't config and volatile-config cluster-wide?
Was there a support meeting about this?
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.
it's still a draft
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.
We have discussed this, and decided to use "admin cluster bootstrap" command to emphasize the fact that this applies to the whole cluster.
|
||
void TCommandClusterBootstrap::Config(TConfig& config) { | ||
TYdbCommand::Config(config); | ||
config.Opts->AddLongOption("guid", "Self-assembly UUID") |
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.
GUID / UUID
Maybe we should stick to one terminology?
9a54e3c
to
db34672
Compare
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
db34672
to
9f0e266
Compare
9f0e266
to
478fbe8
Compare
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
478fbe8
to
e0c3402
Compare
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
e0c3402
to
f29b764
Compare
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
f29b764
to
d44111b
Compare
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
d44111b
to
bab9bf2
Compare
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
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.
CLI part LGTM
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
auto request = MakeRequest<Ydb::BSConfig::BootstrapClusterRequest>(); | ||
request.set_self_assembly_uuid(selfAssemblyUUID); | ||
|
||
return RunSimple<Ydb::BSConfig::V1::BSConfigService, Ydb::BSConfig::BootstrapClusterRequest, |
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.
А почему RunSimple без TRpcRequestSettings вызывается? Клиент получается прокинуть клиентский таймаут не сможет
@@ -46,6 +46,9 @@ class TStorageConfigClient { | |||
// Fetch current cluster storage config | |||
TAsyncFetchStorageConfigResult FetchStorageConfig(const TStorageConfigSettings& settings = {}); | |||
|
|||
// Bootstrap cluster with automatic configuration | |||
TAsyncStatus BootstrapCluster(const TString& selfAssemblyUUID); |
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.
ReplaceStorageConfig и BootstrapCluster вызываются без settings. Так нельзя, любой вызов через SDK должен иметь как минимум TSimpleRequestSettings
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.
И еще это скорее не к тебе вопрос, но почему TStorageConfigSettings наследуется от TOperationRequestSettings? Это специфичные настройки, тут они не используются явно
Changelog entry
Public API bootstrap command
Changelog category
Additional information
"ydb admin cluster bootstrap" command has been added to public API.