Since initial sync between non-wiredTiger and wiredTiger members in a
replica set is performed on a per-document level (and not by copying the
files), this should be possible…
It is possible to mix different storage engines in a replica set, but it is
currently not possible (as of MongoDB 3.2) to set different storage engine
*options* for a collection in a replica set. I.e., if you specify a
collection to use the snappy compressor, the collection will be using
snappy across all secondaries as well (since collection creation options
are replicated to the secondaries).
You received this message because you are subscribed to the Google Groups "mongodb-user"