Skip to content

Support runtime configuration of maxWaitTimeInMinutes - #1784

Merged
tommystendahl merged 2 commits into
masterfrom
feature/issue-1783-runtime-max-wait-time
Sep 3, 2026
Merged

Support runtime configuration of maxWaitTimeInMinutes#1784
tommystendahl merged 2 commits into
masterfrom
feature/issue-1783-runtime-max-wait-time

Conversation

@tommystendahl

Copy link
Copy Markdown
Collaborator

Expose the JMX repair timeout (maxWaitTimeInMinutes) through the existing runtime config endpoint (PATCH /repair-management/v2/config) and the ecctool config command, so operators can tune it without restarting.

  • Add setMaxWaitTimeInMinutes(int) to DistributedJmxProxyFactory; make the field volatile with a validated setter (rejects <= 0) in the impl
  • Expose DistributedJmxProxyFactory as a Spring @bean so the REST controller can inject it
  • Handle the max_wait_time_minutes key in ConfigManagementRESTImpl (validate, apply, and include in the response)
  • Add --max-wait-time flag to ecctool config and include the key in the PATCH body
  • Document the new flag in ECCTOOL.md and ECCTOOL_EXAMPLES.md

New repairs pick up the value immediately; in-flight repairs keep the timeout captured at task creation. Changes are in-memory only and revert to ecc.yml on restart, consistent with the other runtime-configurable scheduler parameters (#1638).

Expose the JMX repair timeout (maxWaitTimeInMinutes) through the existing
runtime config endpoint (PATCH /repair-management/v2/config) and the
ecctool config command, so operators can tune it without restarting.

- Add setMaxWaitTimeInMinutes(int) to DistributedJmxProxyFactory; make the
  field volatile with a validated setter (rejects <= 0) in the impl
- Expose DistributedJmxProxyFactory as a Spring @bean so the REST controller
  can inject it
- Handle the max_wait_time_minutes key in ConfigManagementRESTImpl
  (validate, apply, and include in the response)
- Add --max-wait-time flag to ecctool config and include the key in the
  PATCH body
- Document the new flag in ECCTOOL.md and ECCTOOL_EXAMPLES.md

New repairs pick up the value immediately; in-flight repairs keep the
timeout captured at task creation. Changes are in-memory only and revert
to ecc.yml on restart, consistent with the other runtime-configurable
scheduler parameters (#1638).
@tommystendahl tommystendahl self-assigned this Sep 3, 2026
@tommystendahl tommystendahl added the enhancement New feature or request label Sep 3, 2026
@tommystendahl
tommystendahl requested a review from a team as a code owner September 3, 2026 14:02
@tommystendahl tommystendahl linked an issue Sep 3, 2026 that may be closed by this pull request
@tommystendahl
tommystendahl merged commit e59cf2a into master Sep 3, 2026
351 of 372 checks passed
@tommystendahl
tommystendahl deleted the feature/issue-1783-runtime-max-wait-time branch September 4, 2026 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support runtime configuration of maxWaitTimeInMinutes

2 participants