Details
-
Bug
-
Resolution: Won't Do
-
Major - P3
-
None
-
Linux
*Location*: https://docs.mongodb.com/manual/core/inmemory/
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
*Screen Resolution*: 1536 x 864
Description
Need information on the limitations and gotchas of the sharded cluster deployment option where one or more of the shards are running WiredTiger and other shards are running the in-memory storage engine. For examples: What gets persists in such a configuration? Does the entire contents of the data in the WiredTiger engine have to fit in memory of the in-memory shards?