-
Sub-task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
1
-
Not defined
The changes around the index management for process instances should be broadcast in such as way that it is clear that how Optimize stores instances. This extends to configuration changes too.
ATs:
- We document configuration changes
- We document appropriate index management changes
- We document any resulting limitations
- External variables?
- History cleanup?
- https://docs.camunda.org/optimize/latest/technical-guide/setup/installation/#how-your-data-influences-elasticsearch-requirements - this needs updating with current information
- Explain that archive instance still have single shards whereas the "warm" index continue to use the configured value