01489eehtrri9700kqgo2k238ni5o152 · 12 rows
| key | value |
|---|---|
| auto_compact_enabled | false |
| compact_batch_size | 50 |
| compact_parallel_workers | 5 |
| compact_tier1_days | 30 |
| compact_tier1_dep_levels | 2 |
| compact_tier2_commits | 100 |
| compact_tier2_days | 90 |
| compact_tier2_dep_levels | 5 |
| compaction_enabled | false |
| issue_prefix | tarantool-etcd |
| kv.memory.self-hosted-etcd-config-coldboot | A Tarantool EE cluster can host its own etcd config store (every node runs app.roles.etcd, KV replicated under Raft), but it CANNOT cold-boot from it: the EE config.etcd source fetches over the network at collect time, before box.cfg/replication/role-apply, so with all nodes down nobody serves etcd and nobody can fetch config — circular. Works on ROLLING restart (2/3 peers keep serving). Practical resolution: retain the local cluster-config.yaml as a cold-boot seed. Also: the config.etcd boot Range is linearizable, so set roles_cfg.app.roles.etcd.replicaset.read_pref=any or a follower bounces it with UNAVAILABLE. Demonstrated in examples/tarantool-ee-self-hosted-etcd (phases 1-2 verified on Community 3.8; migrate/reload need EE). |
| kv.memory.tarantool-ee-uses-etcd-as-a-centralized-config | Tarantool EE uses etcd as a centralized-config backend (config.storage / etcd source in TT 3.x): on boot it reads config from etcd then opens a Watch with prev_kv set to diff old-vs-new config on live reload. So Watch prev_kv is a first-class ecosystem consumer, not just a conformance checkbox — it gates drop-in TT EE compatibility. Feature is implemented (app/etcd/watch.lua lookup_prev_kv); the open work is the TestWatchWithPrevKV conformance case (tarantool-etcd-9z2, Phase 5f). |