needsRefresh flag is not checked on catalogue cache's onStaleShardVersion

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.0-rc0, 4.7.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06
    • 9
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There is a check on catalogue cache that sets as needRefresh the RoutingInfoCache of a collection.

      Before setting the flag, the function makes sure that the collection haven't been dropped, however this is not enough. We could've marked the cache as needsRefresh from another thread, which causes the server to crash as we have seen on some build failures.

      Besides checking if the collection was dropped, we should check if the needsRefresh flag was already set.

            Assignee:
            Blake Oler
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: