Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-564

Add support for majority read concern level to MapReduce

    • Type: Icon: New Feature New Feature
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Component/s: None
    • Labels:
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      RUST-102 Duplicate
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion RUST-102 Duplicate

      For SERVER-20214 we are removing support for majority read concern level in these operations because we cannot write in that mode. This ticket is to reenable support.

      The current plan is to emulate majority read concern level by waiting for w:majority in the portions of those operations that write (aggregations including $out and all map reduces) and keep the read concern level for the portions that don't (aggregations not including $out including all work from the shard phase). It is unclear right now which category inline map reduce falls under. Part of this work is to ensure that this approach is valid.

            Unassigned Unassigned
            kyle.suarez@mongodb.com Kyle Suarez
            0 Vote for this issue
            7 Start watching this issue