Use kStrictlyNotIdempotent instead of kNoRetry in cluster command kill op

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Resilience
    • Fully Compatible
    • ALL
    • Workload Resilience 2025-10-27, Workload Resilience 2025-11-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Cluster command kill op still use kNoRetry. The passthrough found that the server failed to retry some operation related to kill running operations.

            Assignee:
            Guillaume Racicot
            Reporter:
            Guillaume Racicot
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: