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

Passing in w: NaN for write concern is interpreted as w: 0

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • Replication
    • ALL

    Description

      As part of the NaN conversion audit of replication, we found that passing in w: NaN as an argument for setting write concern, the NaN is evaluated as 0. This is because we use safeNumberLong() to extract the "w" value, and this function evaluates NaN as 0.

      This issue exists all the way back to 4.4.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              ali.mir@mongodb.com Ali Mir
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: