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

Do not clear the cached sharding filtering information on replication state changes

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.6.0
    • Fix Version/s: 3.6.2, 3.7.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2017-12-18
    • Case:

      Description

      Prior to version 3.6, the shard secondaries did not support filtering based on the active chunk metadata and were required to not have any filtering metadata cached. Because of this on every replication state change we were clearing it "just in case" - step up / step down.

      With support for filtering in 3.6 this is no longer necessary and it also has negative performance impact due to the need to fetch the full metadata, so we should get rid of it.

        Attachments

          Activity

            People

            Assignee:
            kaloian.manassiev Kaloian Manassiev
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: