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

Make all code paths returning StaleConfig error go through the StaleConfigInfo serializer

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.1, 4.1.1
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • v4.0
    • Sharding 2018-07-02

      Currently there are code paths, which manually construct the components for the StaleConfigInfo error. Because of this it is difficult to rely on its contents being populated, which leads to code like this. As part of this ticked, all such places should be identified and changed to use the StaleConfigInfo serialization.

      In addition, since the stale_config library depends on functionality which happens to be in the headers of common_s, specifically, ChunkVersion. Because of this, it needs to repeat the serialization logic of ChunkVersion. We should merge these two libraries (by folding stale_config into common_s) and should use the ChunkVersion serialization logic for StaleConfigInfo.

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

              Created:
              Updated:
              Resolved: