Do not restrict updates to execution control server parameters based on the currently running algorithm

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-10-27, CAR Team 2025-11-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, the ability to update certain execution control server parameters depends on the value of storageEngineConcurrencyAdjustmentAlgorithm. For example, when throughputProbing is active, the parameter storageEngineConcurrentWriteTransactions cannot be updated.

      We should allow changes to these server parameters regardless of the active algorithm.

       

      For instance, when a user switches from throughputProbing to fixedConcurrentTransactions, the transition currently uses the default values of storageEngineConcurrentWriteTransactions and storageEngineConcurrentReadTransactions to resize the ticket pool. Because the user cannot modify these parameters until after the algorithm has changed, the transition may not reflect the desired configuration immediately. Allowing these parameters to be updated at any time would enable a smoother transition and remove the need to wait for default values to be applied before adjusting them.

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: