ClusterServerParameterOpObserver unnecessarily executes during initial sync

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Cluster parameters are already refreshed from storage onConsistentDataAvailable, which is called once initial sync is finished. It seems unnecessary to be updating the in-memory state on the op observer on inserts during initial sync cloning, and in general to be doing anything with the in-memory state while isDataConsistent is false.

              Assignee:
              Unassigned
              Reporter:
              Yujin Kang Park
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: