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

Investigate if we can remove a lock ordering conflict in RangeDeleterServiceOpObserver

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2025-03-03, CAR Team 2025-03-17, CAR Team 2025-03-31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-99150 we've implemented a lock ordering conflict detector.

      Similar to SERVER-99703 we have a conflict of an operation holding a lock on the config database proceeding to lock a user database. Other OpObservers like the preimages one take the locks on the opposite order, having a lock on the user database first then proceeding to take a lock on the config database.

      As in SERVER-99703 we don't suspect this to be a problem since the locks are intent locks but we still should verify there's nothing of concern

            Assignee:
            silvia.surroca@mongodb.com Silvia Surroca
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: