config: new `skip_replication_names` compat option
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Related dev. issue(s): https://github.com/tarantool/tarantool/pull/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 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the root document at reference/reference_lua/compat/#options and review how compatibility options are described. Use the related development pull request for context, then document skip_replication_names with its new and old behavior and upgrade purpose; done means the option is clearly covered in the compatibility reference.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100