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

Avoid race conditions during recoverRefreshShardVersion

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Linked BF Score:
      27

      Description

      Currently, there is no warranty that a collection state is not going to change after refreshing its filtering metadata and before acquiring the lock to cleanup the recover/refresh future.

      The forceShardFilteringMetadataRefresh call should ideally be replaced by a method not acquiring locks, in order to not serialize other collection operations on it.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              pierlauro.sciarelli Pierlauro Sciarelli
              Reporter:
              pierlauro.sciarelli Pierlauro Sciarelli
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: