Skip to content

fix: MM and Indexer should remember disabled status.#19368

Merged
gianm merged 1 commit intoapache:masterfrom
gianm:mm-remember-disabled
Apr 24, 2026
Merged

fix: MM and Indexer should remember disabled status.#19368
gianm merged 1 commit intoapache:masterfrom
gianm:mm-remember-disabled

Conversation

@gianm
Copy link
Copy Markdown
Contributor

@gianm gianm commented Apr 23, 2026

Currently when a MiddleManager or Indexer is disabled via API, the state is stored only in-memory. If it is restarted, the disabled flag is cleared. This is not desirable; it should only be cleared by an operator explicitly re-enabling the server.

This patch fixes it by saving the state to a file.

Currently when a MiddleManager or Indexer is disabled via API, the
state is stored only in-memory. If it is restarted, the disabled flag
is cleared. This is not desirable; it should only be cleared by an
operator explicitly re-enabling the server.

This patch fixes it by saving the state to a file.
@gianm gianm merged commit b442161 into apache:master Apr 24, 2026
113 of 116 checks passed
@gianm gianm deleted the mm-remember-disabled branch April 24, 2026 00:06
@github-actions github-actions Bot added this to the 38.0.0 milestone Apr 24, 2026
gianm added a commit that referenced this pull request Apr 24, 2026
PR #19368 updated the enabled/disabled state of an MM or Indexer to
persist across restarts. In some cases, such as disabling a server
before doing an in-place restart, it is more convenient to
automatically re-enable on restart.

This patch adds a config parameter to restore the old behavior:
druid.worker.startAlwaysEnabled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants