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

Make fsync_lock_unlock.js compatible with embedded router

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • Cluster Scalability 2024-4-29
    • 51

      When run against an embedded router, the insert that the assert.soon() currentOp in this test is expected to trigger a CatalogCache refresh that is expected to get stuck in performNoopMajorityWriteLocally() here because the mongod is fsync locked. That is, this is the same issue as described in SERVER-83433.

      The router service on mongod currently uses the ShardServerCatalogCacheLoader (SERVER-82588). So when a refresh occurs, it requires doing a noop write which will then deadlock since the mongod is fsync locked. This deadlock should go away after SERVER-82588.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: