config: start singleton instance in RW by default
Enabling read-write by default is unsafe for an instance in a replicaset with more than one instance. The only meaningful default here is read-only. On the other hand, a signleton instance (the only one in its replicaset) almost always started in the read-write mode in practice. Let's use these values as defaults for these situations. The name of the option is changed from `rw` (boolean) to `mode` (enum with allowed values `'ro'` and `'rw'`). We agreed on the enum after a long controversy whether it should be `ro` or `rw`. Part of #8810 NO_DOC=the old behavior was not released, the documentation request will be registered manually NO_CHANGELOG=see NO_DOC
Showing
- doc/examples/config/etcd/remote.yaml 1 addition, 1 deletiondoc/examples/config/etcd/remote.yaml
- doc/examples/config/replicaset.yaml 1 addition, 1 deletiondoc/examples/config/replicaset.yaml
- doc/examples/config/single.yaml 1 addition, 3 deletionsdoc/examples/config/single.yaml
- src/box/lua/config/applier/box_cfg.lua 23 additions, 1 deletionsrc/box/lua/config/applier/box_cfg.lua
- src/box/lua/config/instance_config.lua 15 additions, 4 deletionssrc/box/lua/config/instance_config.lua
- test/config-luatest/appliers_test.lua 1 addition, 5 deletionstest/config-luatest/appliers_test.lua
- test/config-luatest/basic_test.lua 13 additions, 7 deletionstest/config-luatest/basic_test.lua
- test/config-luatest/cluster_config_schema_test.lua 4 additions, 4 deletionstest/config-luatest/cluster_config_schema_test.lua
- test/config-luatest/config_test.lua 7 additions, 15 deletionstest/config-luatest/config_test.lua
- test/config-luatest/instance_config_schema_test.lua 13 additions, 2 deletionstest/config-luatest/instance_config_schema_test.lua
- test/config-luatest/sources_test.lua 1 addition, 5 deletionstest/config-luatest/sources_test.lua
Loading
Please register or sign in to comment