Config limitation: names can't be changed after the cluster is bootstrapped
Open
Nobody has claimed this yet.
3.0
config
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Tarantool
Since: 3.0
Root document:
- https://www.tarantool.io/en/doc/latest/platform/configuration/
- https://www.tarantool.io/en/doc/latest/reference/configuration/configuration_reference/
SME: @ Totktonada
Details
Request from delivery: add info that the names of cluster elements – groups, replica sets, instances – can't be changed after the cluster has started.
TODO: find out the exact moment after which these names cant' be changed.
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
Start with the configuration documentation at the two linked root documents and determine the exact point after cluster bootstrap when group, replica set, and instance names become immutable. Update the relevant documentation to state that limitation and the precise timing, then verify the wording against the documented configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100