Colleagues, we’re using CouchBase for many use-cases, one of those: session storage.
And we would very much like to survive 1 node failures, so we need replication.
After 1 node fails we will rely on auto-failover to remove it and promote replicas to active.
Then we think we’ll do rebalance and continue live happily [until next problem :)].
But we do not care for complete power outage and we do not need persistence.
Persistence in 2.0 version became very HDD hungry and we don’t like that at all.
We came across several hints that persistence is integral part of CouchBase but that is totally counterintuitive. One thinks of replication queues and disk persistence queues as separate entities.
(One reference here: Stop writing data to disk in couchbase)
(With advice to consider memcached bucket type; not applicable to our use-case, since we need replication)
Please clarify, if it is possible to disable persistence in any way?
Alexander, Russia, Moscow