`replication.bootstrap_strategy` = `native`

[TarantoolBot]

Related dev. issue(s): tarantool/tarantool#10857
Product: Tarantool
Since: 3.4
Root document: https://www.tarantool.io/en/doc/latest/reference/configuration/#cfg-replication-bootstrap-strategy
SME: @ sergepetrenko

Details

The new bootstrap strategy native is supported since the 3.4.0
release. It can be enabled using the replication.bootstrap_strategy
option in the YAML configuration.

Dev issue: tarantool/tarantool#10857

The new strategy acts more or less similar to the auto strategy, but
relaxes its limitations (see details in the linked dev issue).

It is based on the supervised strategy and mainly performs two things:

• issues box.ctl.make_bootstrap_leader({graceful = true}) to bootstrap
  a replicaset
• issues box.ctl.make_bootstrap_leader() to keep the bootstrap leader
  record pointing to the instance that is currently in the RW mode (to
  register new replicas)

The choice how to choose a bootstrap leader to initialize the replicaset
depends on the replication.failover option. See details in the linked
dev issue.
Requested by @ Totktonada in tarantool/tarantool@c36d3c0.

[lenkis]

The native strategy is the recommended choice for highly dynamic clusters with
automatic scaling, as well as in most other cases.

The only scenario when this strategy may work worse than auto is when a current
bootstrap leader in a multi-master configuration goes off or becomes inaccessible.
Another RW instance doesn't pick up this role automatically and some RW -> RO -> RW
configuration changes are needed to make another instance take the role. In this regard,
the native strategy seems worse than auto.