Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
-
*Location*: https://docs.mongodb.org/v3.0/tutorial/change-oplog-size/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36
*Referrer*: https://www.google.com/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: tutorial/change-oplog-size
*Location*: https://docs.mongodb.org/v3.0/tutorial/change-oplog-size/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36 *Referrer*: https://www.google.com/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: tutorial/change-oplog-size
-
0.25
Description
Would it make sense to point out that nodes should be un-managed by Cloud when going through these steps? We just followed this tutorial and found it really useful. We had to suspend automation for the single secondary node we were updating and resume automation afterwards, which I don't see mentioned anywhere (although it was sort of obvious).
Maybe if not adding those exact steps, we could have a note that if your nodes are cloud-managed, doing this will break things.
cc brian.samek