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

profiling can throw stale config after write

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Write Ops
    • None
    • ALL

    Description

      Because profiling takes a context for the namespace of the operation and write commands do not use setShardVersion, it's possible for a write to be successful but profiling to throw a stale config error. This aborts the rest of the batch.

      Issue probably exists in previous versions of mongodb when the database lock of a write is released before profiling, but would require a version change during that interval in order to manifest.

      Attachments

        Activity

          People

            greg_10gen Greg Studer
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: