Operational Defect Database

BugZero found this defect 2412 days ago.

MongoDB | 406458

[SERVER-30240] remove incorrect paragraph from getNextOpTime() comments in oplog.cpp

Last update date:


Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:




The follow paragraph is no longer true and should be removed. We should link this ticket to the SERVER ticket in which this assumption changed. https://github.com/mongodb/mongo/blob/878e55a460de02de2f0171d3e9e1bcfc12bb80cc/src/mongo/db/repl/oplog.cpp#L148 oplog.cpp 143 /** 144 * Allocates an optime for a new entry in the oplog, and updates the replication coordinator to 145 * reflect that new optime. Returns the new optime and the correct value of the "h" field for 146 * the new oplog entry. 147 * 148 * NOTE: From the time this function returns to the time that the new oplog entry is written 149 * to the storage system, all errors must be considered fatal. This is because the this 150 * function registers the new optime with the storage system and the replication coordinator, 151 * and provides no facility to revert those registrations on rollback. 152 */ 153 void getNextOpTime(OperationContext* opCtx, 154 Collection* oplog, 155 ReplicationCoordinator* replCoord, 156 ReplicationCoordinator::Mode replicationMode, 157 unsigned count, 158 OplogSlot* slotsOut) {

Top User Comments

xgen-internal-githook commented on Fri, 21 Jul 2017 12:44:31 +0000: Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'} Message: SERVER-30240 Remove obsolete comment in oplog.cpp. This comment was obsoleted by SERVER-15192. Branch: master https://github.com/mongodb/mongo/commit/405b07f373d900e810965a838f1c4bbaf8b16dcb

Additional Resources / Links


BugZero Risk Score

Coming soon



Have you been affected by this bug?


Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.


Login to read and write comments.

Have you ever...

had your data corrupted from a