Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
*Location*: https://docs.mongodb.org/manual/core/replica-set-rollbacks/#rollback-limitations
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36
*Screen Resolution*: 1920 x 1200
*repo*: docs
*source*: core/replica-set-rollbacks
*Location*: https://docs.mongodb.org/manual/core/replica-set-rollbacks/#rollback-limitations *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36 *Screen Resolution*: 1920 x 1200 *repo*: docs *source*: core/replica-set-rollbacks
-
0.25
Description
The limitations part referring to 300MB of data refers to the data which needs to be retrieved from the upstream source (like updates or deleted docs which must be rolled back) not any inserted docs (which will be saved to the rollback files) which must be removed during the rollback.
For a largely insert workload this may result in very large rollback files.