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

MetadataManager directly calls into the CatalogCache

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.3, 4.1.1
    • Affects Version/s: 4.1.1
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 2018-07-02

      The MetadataManager class, which contains the sharding filtering information incorrectly references the catalog cache. This is wrong because if the cache doesn't contain the filtering information for the specified collection, it will return empty filtering information, which may lead to incorrect results from being returned.

      This is not a problem in 4.0 because the createMetadataAt method is not used, but will be in 4.2 when we start supporting sharded read-only transactions.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: