Description
<…> find the full example here: config_etcd.
Starting a cluster
**|The tt utility is the recommended way to start Tarantool instances.
You can learn how to do this from the Starting and stopping instances section.
You can also use the tarantool command to start a Tarantool instance.
In this case, you can eliminate creating a local configuration and provide connection settings using the following environment variables:Tarantool-based storage: TT_CONFIG_STORAGE_ENDPOINTS and TT_CONFIG_STORAGE_PREFIX.
etcd-based storage: TT_CONFIG_ETCD_ENDPOINTS and TT_CONFIG_ETCD_PREFIX.The example below shows how to provide etcd connection settings and start cluster instances using the tarantool command:
$ export TT_CONFIG_ETCD_ENDPOINTS=http://localhost:2379
$ export TT_CONFIG_ETCD_PREFIX=/myapp$ tarantool --name instance001
$ tarantool --name instance002
$ tarantool --name instance003|**Reloading configuration
By default, Tarantool watches keys <…>
https://www.tarantool.io/en/doc/latest/platform/configuration/configuration_etcd/#starting-a-cluster
Running the code using the etcd setup from above won't work. The authentication is enabled but the user isn't specified when starting tarantool instances. Tarantool instances won't start.
In this case either the etcd authorization should be disabled. It means the section https://www.tarantool.io/en/doc/latest/platform/configuration/configuration_etcd/#etcd-based-storage should be skipped because it's impossible to use the environment variables to specify the user.
Probably it's meant to be understood like that though it isn't clear from the first glance. IMO it should be stated explicitly.