Skip to content

docs: clarify disabling Optimize/legacy exporter requires an actuator disable #6455

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
eamonnmoloney wants to merge 2 commits into
base: main
Choose a base branch
from
+33 −0
Open

docs: clarify disabling Optimize/legacy exporter requires an actuator disable #6455

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8bef704
docs: note that disabling Optimize/legacy exporter needs actuator dis…
eamonnmoloney Jun 25, 2026
e0b1cdd
docs: cite the 8.9.3 / 8.10.0 patches that include the exporter fix
eamonnmoloney Jun 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions charts/camunda-platform-8.10/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,17 @@
> [migration from Bitnami guide](https://docs.camunda.io/docs/self-managed/deployment/helm/operational-tasks/migration-from-bitnami/)
> and its accompanying toolkit for moving each component to externally managed infrastructure.

> [!IMPORTANT]
> **Disabling Optimize or the legacy Elasticsearch/OpenSearch exporter via Helm values does not stop the running exporter.**
> Setting `optimize.enabled: false` (or `orchestration.exporters.zeebe.enabled: false`) only removes the legacy exporter from
> the broker's *static* configuration. The broker reconciles that removal into its *dynamic* cluster configuration, but the
> reconciliation runs only on partition leaders and relies on cluster gossip to converge across all brokers. If it does not
> converge, the exporter can remain stuck in an `UNKNOWN` / `CONFIG_NOT_FOUND` state, which halts log compaction and grows the
> Zeebe PVC. After disabling Optimize or the legacy exporter, explicitly disable the running exporter on each broker via
> `POST /actuator/exporters/{elasticsearch|opensearch}/disable` and confirm convergence with `GET /actuator/exporters`
> (every broker should report `DISABLED`). Ensure your Camunda version includes the exporter-state reconciliation fix
> ([camunda/camunda#52260](https://github.com/camunda/camunda/issues/52260), fixed in 8.10.0-alpha2, so all 8.10.x releases include it).

Please also refer to the [documentation](https://docs.camunda.io/docs/self-managed/setup/overview/) on how to use Helm charts.

- [Architecture](#architecture)
Expand Down
11 changes: 11 additions & 0 deletions charts/camunda-platform-8.8/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,16 @@
# Camunda 8 Helm Chart

> [!IMPORTANT]
> **Disabling Optimize or the legacy Elasticsearch/OpenSearch exporter via Helm values does not stop the running exporter.**
> Setting `optimize.enabled: false` (or `orchestration.exporters.zeebe.enabled: false`) only removes the legacy exporter from
> the broker's *static* configuration. The broker reconciles that removal into its *dynamic* cluster configuration, but the
> reconciliation runs only on partition leaders and relies on cluster gossip to converge across all brokers. If it does not
> converge, the exporter can remain stuck in an `UNKNOWN` / `CONFIG_NOT_FOUND` state, which halts log compaction and grows the
> Zeebe PVC. After disabling Optimize or the legacy exporter, explicitly disable the running exporter on each broker via
> `POST /actuator/exporters/{elasticsearch|opensearch}/disable` and confirm convergence with `GET /actuator/exporters`
> (every broker should report `DISABLED`). Ensure your Camunda version includes the exporter-state reconciliation fix
> ([camunda/camunda#52260](https://github.com/camunda/camunda/issues/52260), backported to 8.8.25).

Please also refer to the [documentation](https://docs.camunda.io/docs/self-managed/setup/overview/) on how to use Helm charts.

- [Architecture](#architecture)
Expand Down
11 changes: 11 additions & 0 deletions charts/camunda-platform-8.9/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,16 @@
# Camunda 8 Helm Chart

> [!IMPORTANT]
> **Disabling Optimize or the legacy Elasticsearch/OpenSearch exporter via Helm values does not stop the running exporter.**
> Setting `optimize.enabled: false` (or `orchestration.exporters.zeebe.enabled: false`) only removes the legacy exporter from
> the broker's *static* configuration. The broker reconciles that removal into its *dynamic* cluster configuration, but the
> reconciliation runs only on partition leaders and relies on cluster gossip to converge across all brokers. If it does not
> converge, the exporter can remain stuck in an `UNKNOWN` / `CONFIG_NOT_FOUND` state, which halts log compaction and grows the
> Zeebe PVC. After disabling Optimize or the legacy exporter, explicitly disable the running exporter on each broker via
> `POST /actuator/exporters/{elasticsearch|opensearch}/disable` and confirm convergence with `GET /actuator/exporters`
> (every broker should report `DISABLED`). Ensure your Camunda version includes the exporter-state reconciliation fix
> ([camunda/camunda#52260](https://github.com/camunda/camunda/issues/52260), backported to 8.9.3).

Please also refer to the [documentation](https://docs.camunda.io/docs/self-managed/setup/overview/) on how to use Helm charts.

- [Architecture](#architecture)
Expand Down
Loading