Skip to content
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.

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

Add documentation for new feature in zeebe Dynamic Cluster Config #4395

Closed
entangled90 opened this issue Oct 4, 2024 · 0 comments · Fixed by #4462
Closed

Add documentation for new feature in zeebe Dynamic Cluster Config #4395

entangled90 opened this issue Oct 4, 2024 · 0 comments · Fixed by #4462
Assignees
Labels
component:zeebe Issues related with Zeebe project target:8.7 Issues included in the 8.7 release

Comments

@entangled90
Copy link
Contributor

See camunda/camunda#15793 for details about the new configuration entries and the descriptions to be added.

@entangled90 entangled90 added component:zeebe Issues related with Zeebe project target:8.7 Issues included in the 8.7 release labels Oct 4, 2024
@entangled90 entangled90 self-assigned this Oct 4, 2024
github-merge-queue bot pushed a commit to camunda/camunda that referenced this issue Oct 9, 2024
## Description
ClusterConfigurationGossiperConfig can be configured in both broker &
gateway profiles. The current hardcoded configuration is used as default
in case it's not configured.

A new namespace in the configuration has been created under
`[zeebe.broker|zeebe.gateway].cluster.dynamicConfig`. At the moment it
contains only one field `gossip`, but it can be used if we need to
extend the configuration.

The configuration is validated using the following criteria:
- syncDelay must be strictly positive
- syncRequestTimeout must be strictly positive
- gossipFanout must be greater or equal than 2
- if enableSync is false, syncDelay & syncRequestTimeout are not
validated

❓ Should enableSync be removed? If yes, should we remove directly in
this PR?

❓ When the broker is started in standalone mode, the gateway will not
start a gossiping the dynamic config as it's already done by the broker,
hence I did not add a specific config in the template under
`zeebe.broker.gateway.cluster.dynamicConfig`.
Is this correct?

<!-- Describe the goal and purpose of this PR. -->

## Checklist
- [X] Issue created: camunda/camunda-docs#4395

## Related issues

closes #15793
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:zeebe Issues related with Zeebe project target:8.7 Issues included in the 8.7 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant