Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30240

remove incorrect paragraph from getNextOpTime() comments in oplog.cpp

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Trivial - P5
    • Resolution: Fixed
    • None
    • 3.5.11
    • Replication
    • None
    • Fully Compatible
    • ALL

    Description

      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) {
      

      Attachments

        Issue Links

          Activity

            People

              schwerin@mongodb.com Andy Schwerin
              benety.goh@mongodb.com Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: