Skip to content

box.cfg.bootstrap_leader accepts instance names now #3504

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

Closed
TarantoolBot opened this issue Jun 8, 2023 · 1 comment · Fixed by #3834
Closed

box.cfg.bootstrap_leader accepts instance names now #3504

TarantoolBot opened this issue Jun 8, 2023 · 1 comment · Fixed by #3834
Assignees
Labels
3.0 config replication [area] Related to Replication

Comments

@TarantoolBot
Copy link
Collaborator

The option box.cfg.bootstrap_leader, which specifies the desired
bootstrap leader when bootstrap_strategy is "config" now accepts
instance names.

For example, this is a valid config without replication:

box.cfg{
    instance_name = 'main-server',
    bootstrap_strategy = 'config',
    bootstrap_leader = 'main-server'
}

When box.cfg contains some entries in replication, the node will
bootstrap from the node which has the instance name specified in
box.cfg.bootstrap_leader.

This is an addition to #3432
Requested by @sergepetrenko in tarantool/tarantool@8ceef02.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0 config replication [area] Related to Replication
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants