Different storage engines for part of nodes in replicaset #2119
Description
Proposal
Way to configure through CR different storage engines for part (hidden, non-voting) of nodes in replicaset
Use-Case
With this deployment model, persisten storage for in-memory can be achieved. Clients connect only to the in-memory storage engine mongod instances. Even if both mongod instances running in-memory storage engine crash and restart, they can sync from the member running WiredTiger storage engine. The hidden mongod instance running with WiredTiger persists the data to disk, including the user data, indexes, and replication configuration information.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response