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

$listCatalog doesn't respect readConcern

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • v7.1, v7.0
    • CAR Team 2023-11-13, CAR Team 2023-11-27

      Say we rename a collection a collection and the rename has only been applied to a minority of nodes in a replica set. That is, the majority timestamp hasn't yet advanced.

      If a user were to perform $listCatalog targeting the old collection name with majority readConcern then the aggregation will fail since it is now checking against the latest version of the catalog instead of respecting the read concern.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: