Avoid checkLogEntryRWC to match Slow in-progress query logs that lack applied writeConcern.w

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.0.1, 9.0.2
    • Affects Version/s: 9.0.0-rc1
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v9.0
    • CAR Team 2026-08-31
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      checkLogEntryRWC in jstests/sharding/read_write_concern_defaults_application.js selects the first global-log line that contains the command comment and the substring "writeConcern". That can match nested command.writeConcern on a Slow in-progress query, which does not yet have top-level attr.writeConcern.
      The assertion then checks attr.writeConcern.w === "majority" and fails with expected undefined to equal "majority".

      Parse candidate log lines as JSON and skip Slow in-progress query lines unless attr.writeConcern.w is already present.

            Assignee:
            Anna Maria Nestorov
            Reporter:
            Anna Maria Nestorov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: