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

Investigate banning majority readConcern on sharding catalog access

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Catalog and Routing

    Description

      As part of SERVER-85869 we investigated the possibility of banning majority readConcern from the sharding catalog reads. This is a result of having seen multiple failures that had to be addressed due to reading faulty data.

      One case is SERVER-54874 in which chunks were wrongly being read with majority readConcern, leading to invalid data being returned. Another is SERVER-75490 which had the same issue but now for the checkMetadataConsistency command.

      Considering that the snapshot model is simpler to understand than majority reads we should investigate whether it makes sense to ban majority reads in favor of snapshot ones.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: