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

Get rid of the syncFromConfig argument of the internal command to flush the routing table cache

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31

    Description

      Based on analysis that includes old versions down to 4.0 (latest unsupported version), the syncFromConfig argument of the _flushRoutingTableCacheUpdates command is never set to false. Consequently, all the related logic when set to false can be eliminated.

      Goal of this task is to evaluate that statement and possibly get rig of the related logic.

      Based on an analysis that includes older versions up to 4.0 (latest version not supported), the syncFromConfig argument of the _flushRoutingTableCacheUpdates command is never set to false. As a result, all related logic when set to false can be removed.

      The goal of this task is to evaluate that statement, possibly remove the argument and change the related logic assuming it is always true.

      Open questions:
      1. Is this command used only internally between the cluster processes?
      2. Is this used by our support team?
      3. In that case, do they pass the syncFromConfig argument and why?

      Attachments

        Activity

          People

            antonio.fuschetto@mongodb.com Antonio Fuschetto
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: