We have an undocumented configuration option rocksdb_secondary which allows for multiple instances of Tuwunel in a single-writer multiple-reader topology. The synchronization is undeveloped, so the readers will be stuck at a snapshot from when they were started. This filesystem-level clustering, though primitive, is a highly economical path to provide:
- Failover for uninterrupted service on server failure or upgrade.
- Load-shedding to exceed the vertical limitation of a provider (i.e. when 64 or 128 cores is not enough). Requests to Matrix protocol GET/read-only endpoints can be balanced over the cluster of secondaries.
We have an undocumented configuration option
rocksdb_secondarywhich allows for multiple instances of Tuwunel in a single-writer multiple-reader topology. The synchronization is undeveloped, so the readers will be stuck at a snapshot from when they were started. This filesystem-level clustering, though primitive, is a highly economical path to provide: