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

Ensure cluster-wide parameters mechanism correctness (when working with query settings parameter)

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • QE 2023-07-24, QE 2023-08-21, QE 2023-09-04, QE 2023-09-18, QE 2023-10-02, QE 2023-10-16, QE 2023-10-30, QE 2023-11-13, QE 2023-11-27, QE 2023-12-11, QE 2023-12-25, QE 2024-01-08
    • 4

      querySettings cluster parameter is a special cluster parameter, that suffers from lost update problem.

      Corresponding design doc describes how to mitigate this issue.

      This ticket tracks all the work required to ensure no correctness issues may occur.

        1.
        		 Introduce maxPreviousTime parameter to setClusterParameter command in replica set SERVER-78802 Sub-task Closed Romans Kasperovics 7.2.0-rc0
        2.
        		 Introduce maxPreviousTime parameter to setClusterParameter command in sharded clusters SERVER-78803 Sub-task Closed Romans Kasperovics 7.3.0-rc0
        3.
        		 Prevent setClusterParameters being called on querySettings parameter SERVER-78804 Sub-task Closed Serhii Lysenko 7.3.0-rc0
        4.
        		 Remove SetClusterParameterInvocation::invoke() overload use in audit_op_observer.cpp SERVER-80534 Sub-task Closed Romans Kasperovics 7.3.0-rc0
        5.
        		 Prevent set-/removeQuerySettings being called in standalone SERVER-81099 Sub-task Closed Romans Kasperovics 7.3.0-rc0

            Assignee:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Reporter:
            denis.grebennicov@mongodb.com Denis Grebennicov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: