Uploaded image for project: 'MongoDB ETL Tools'
  1. MongoDB ETL Tools
  2. TOOLS-1886

oplog restore triggers server log warnings about atomic operations with timestamps

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: mongorestore
    • Labels:
      None

      Description

      When testing mongorestore with an oplog, I see a lot of these in the log when testing against 3.6-rc4.

      2017-11-19T06:13:07.386-0500 D -        [conn15] User Assertion: 226:cannot apply an op with a timestamp in atomic applyOps mode; will retry without atomicity src/mongo/db/repl/apply_ops.cpp 194
      

      The applyOps command is then retried without "atomic" mode and succeeds, so the main effect so far appear to be log clutter.

      Eric Milkie believes we should just remove timestamps. (I wonder if we should do that in mongodump rather than in mongorestore.) Benety Goh points out that there is also an undocumented option to turn off atomic updates. Geert Bosch believes either should be fine.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                backlog-server-tools Backlog - Server Tools Team
                Reporter:
                david.golden David Golden
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: