CollectionIndexUsageTracker must have its own concurrency control without depending on collection level locking

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Execution Team 2020-06-15, Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-07-27, Execution Team 2020-08-24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Per the Lock Free Reads project, collection level locking concurrency control will change, removing read collection IS locks, so reads will no longer conflict with X lock index operations. This will make the internal usage of CollectionIndexUsageTracker's map unsafe.

      Need some new concurrency control in CollectionIndexUsageTracker

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: