Setting throughputProbingInitialConcurrency to match throughputProbingMaxConcurrency fails on validation

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Workload Resilience
    • ALL
    • Workload Resilience 2025-11-24, Workload Resilience 2025-12-08
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This could be a possible bug.

      Setting throughputProbingInitialConcurrency to the same value as throughputProbingMaxConcurrency fails with "Throughput probing initial concurrency cannot be greater than maximum concurrency".

      The value we used is 512 for both parameters.

      Also we tried setting throughputProbingInitialConcurrency to 511 and throughputProbingMaxConcurrency to 512 and the validator failed with the same error.

            Assignee:
            Jiaqi Tian
            Reporter:
            Lubo Blagoev
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: