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

Avoid calling shard server opobserver during recovery procedures

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc5
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2024-05-13, CAR Team 2024-05-27
    • 200

      It seems there is an issue when an initial sync node attempts to acquire collection locks on a view during oplog replay. The lock acquisition would fail with CommandNotSupportedOnView. This results in updates/deletes not being applied correctly on the initial syncing node, leading to data inconsistency.

      To resolve this, we should ensure that the shard server op observer does not run during recovery procedures. It looks like today we skip running the shard server op observer functions only if the node is standalone or primary.

            Assignee:
            yujin.kang@mongodb.com Yujin Kang Park
            Reporter:
            xuerui.fa@mongodb.com Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: