Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
None
Description
The documentation for changing the OpLog size mentions that you should bring down the current Primary then change the size. This is more intrusive than taking down the Secondaries one after the other and changing the oplog size there, as with the Rolling Index rebuild instructions.
The docs also mention to shut down the node, rather than step down first. This could lead to a situation where the Secondaries are not up to date with the Primary before the Primary is shut down - if an rs.stepDown() is issued then there will at least be a warning about no nodes being within 10 seconds of the Primary.