Configure operate correctly #84
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adjust the config of operate such that it can be easily enabled for our benchmarks
Zelldon
commented
Aug 23, 2023
| @@ -318,11 +318,11 @@ camunda-platform: | |||
| # RetentionPolicy.zeebeIndexMaxSize can be set to configure the maximum allowed zeebe index size in gigabytes. | |||
| # After reaching that size, curator will delete that corresponding index on the next run. | |||
| # To benefit from that configuration the schedule needs to be configured small enough, like every 15 minutes. | |||
| zeebeIndexMaxSize: 1 | |||
| zeebeIndexMaxSize: 30 | |||
There was a problem hiding this comment.
ℹ️ This is to not delete data too early.
| @@ -336,6 +336,25 @@ camunda-platform: | |||
|
|
|||
| operate: | |||
| enabled: false | |||
| image: | |||
| tag: 8.2.8 | |||
There was a problem hiding this comment.
💭 Do we really want to fix the Operate version? Shouldn't we use the same version as we use for the rest of camunda-platform?
There was a problem hiding this comment.
Actually we don't want to fix it, but we might need to set it separately in the benchmark workflows. We also need to make sure they can create docker images on the fly. Which is an open TODO https://github.com/camunda/operate/issues/5178
lenaschoenburg
approved these changes
Aug 24, 2023
In order to test operate templates probably we have to add some prefixes to the golden files. Done this on all other tests as well to not conflict with other files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adjust the config of operate such that it can be easily enabled for our benchmarks. Per default it is still disabled.
I used and tested this config recently see https://github.com/camunda/zeebe/tree/cqjawa-mixed-operate-benchmarks
Related initiative and project https://app.slack.com/client/T0PM0P1SA/C05GGP8C214