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

ScopedShardVersionCriticalSection can leave critical section held if filtering metadata refresh fails

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.0.0-rc0
    • 5.0.0
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • 38

    Description

      If the ScopedShardVersionCriticalSection constructor enters the critical section catchUp phase, but later forceShardFilteringMetadataRefresh fails, the critical section will be left taken because it's constructor won't execute.

      Attachments

        Activity

          People

            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: