Avoid race conditions during recoverRefreshShardVersion

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • 27
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Pierlauro Sciarelli
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: