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

Document breaking change in repository name configuration #4717

Open
Tracked by #3966
entangled90 opened this issue Dec 5, 2024 · 0 comments
Open
Tracked by #3966

Document breaking change in repository name configuration #4717

entangled90 opened this issue Dec 5, 2024 · 0 comments
Labels
component:self-managed Docs and issues related to Camunda Platform 8 Self-Managed target:8.7 Issues included in the 8.7 release

Comments

@entangled90
Copy link
Contributor

entangled90 commented Dec 5, 2024

Because indices have been harmonized, the ES/OS repository name must be the same in all webapps or (if deployed as a single app, only one of the has to be configured)

Context:

If users are deploying the web apps in standalone mode, and they configure different snapshot repository names for each, then the backups will be taken based on which node serves the request.

  • This can mean missing back ups on restore if a different node serves the request.
  • This can mean more expensive back ups since incremental backups would not work as well. It's unclear what was previously the deployment configuration, so we will assume users defined the same name across all apps.
  • We will document that it's important they configure either only one of them, or that all repository name configuration are the same, and we will document why.
  • If users do not read our docs or misconfigure things, then they may have a bad UX, but the backups should still exist they might just be harder to restore.
    -It's unclear how we would move their snapshots from one repository to the other or something like this, but that's the same as if they changed the name after the initial deployment, so...I guess it's OK for now.
@entangled90 entangled90 added target:8.7 Issues included in the 8.7 release component:self-managed Docs and issues related to Camunda Platform 8 Self-Managed labels Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:self-managed Docs and issues related to Camunda Platform 8 Self-Managed target:8.7 Issues included in the 8.7 release
Projects
None yet
Development

No branches or pull requests

1 participant