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

appendMajorityWriteConcern should only override wtimeout if it is non-zero

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Service Arch
    • ALL
    • Service Arch Prioritized List

    Description

      wtimeout of zero has a special meaning that it's no timeout. So, logically it has a greater value than anything, but we use numerical comparisons in the places below:

      https://github.com/10gen/mongo/blob/231d6367ea3c7670a458ce00252d970979d7f5be/src/mongo/executor/async_rpc_util.h#L74
      https://github.com/10gen/mongo/blob/231d6367ea3c7670a458ce00252d970979d7f5be/src/mongo/db/commands.cpp#L509

      So, it ends up being treated as a smaller number. As a result, a no timeout setting can be overwritten with a smaller timeout.

      Attachments

        Activity

          People

            backlog-server-servicearch Backlog - Service Architecture
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: