Related dev. issue(s): tarantool/tarantool#12196
Product: Tarantool
Since: product version
Audience/target: who will read it and for what task?
Root document: https://www.tarantool.io/en/doc/latest/reference/reference_lua/compat/#options
SME: @mandesero @georgiy-belyanin
Details
The compat.skip_replication_names option controls whether Tarantool skips instance and replicaset name handling during replication startup.
new (3.x default): Tarantool applies instance_name and replicaset_name on startup and validates them against the snapshot data.old (2.x default): Tarantool skips applying instance_name and replicaset_name on startup and does not validate them against the snapshot data. This mode is intended for upgrades from Tarantool 2.11, so a Tarantool 3.x+ instance configured via the declarative config can join a 2.11-compatible replicaset where the master snapshot may not contain names.
Related dev. issue(s): tarantool/tarantool#12196
Product: Tarantool
Since: product version
Audience/target: who will read it and for what task?
Root document: https://www.tarantool.io/en/doc/latest/reference/reference_lua/compat/#options
SME: @mandesero @georgiy-belyanin
Details
The
compat.skip_replication_namesoption controls whether Tarantool skips instance and replicaset name handling during replication startup.new(3.x default): Tarantool appliesinstance_nameandreplicaset_nameon startup and validates them against the snapshot data.old(2.x default): Tarantool skips applyinginstance_nameandreplicaset_nameon startup and does not validate them against the snapshot data. This mode is intended for upgrades from Tarantool 2.11, so a Tarantool 3.x+ instance configured via the declarative config can join a 2.11-compatible replicaset where the master snapshot may not contain names.