[Config] Migrating configuration from 2.11 to 3.х

[andreyaksenov]

Product: Tarantool
Since: 3.0
Root document: Releases | 3.0
SME: @ Totktonada

Details

Create a guide that shows how to migrate the Tarantool configuration from the old approach to a new config. This guide may include two parts:

• Basic migration scenarios: https://docs.google.com/document/d/1bH22TuMDuJEp50vwsgGUCBxt3jt22ve6cKgAKDuAumA/edit?usp=sharing
• Full reference for all options: https://docs.google.com/spreadsheets/d/1_yEK9N_hBVWIga9mOk7zZzA6Zd3mAq7e5KZsnrbgj30/edit?usp=sharing

[Totktonada]

(Irrelevant now.)

Tarantool's new startup flow unconditionally passes instance name and replicaset name to the underneath box.cfg() call. It means that upgrading from snapshots without saved instance and replicaset names requires a one-time startup in the force-recovery mode.

We've two tasks planned in these regards:

• Allow to set instance/replicaset/cluster names on recovery at first box.cfg tarantool#8978 (teamS)
• Add --force-recovery CLI option tarantool#8876 (teamL)

[andreyaksenov]

See also: #3219