-
Feature Request
-
Resolution: Done
-
L3 - Default
-
None
Feature description:
- given:
- I have several Optimize instances running with the same version which use the same Elasticsearch instance
- Optimize instance A is used to import the data and offers the user interface to create, edit and delete entities (e.g. reports or dashboards)
- Optimize instance B is configured to only offer the user interface and the import is disabled.
- when:
- Optimize instance A is failing or shutdown (e.g. due to maintenance work)
- then:
- I can still use B to create, edit, update or delete entities in Optimize
- The reports are all based on the current state of the data without new data being imported to Optimize
- such that:
- The user has the possibility to always ensure a version of Optimize up and running, so in case one instance fails, the other one can take over.
AT:
- optimize can be run clustered with two or more instances
- the cluster setup specifics are documented (dedicated guide + new config params)
Hint:
- Make sure that there are no conflicts during the index creation while running multiple instances in parallel
- When the import is disabled the status api should return that Optimize is currently not importing
- It should be documented how the clustering works, what are the use-cases and limitation of it
This is the controller panel for Smart Panels app
1.
|
Disable import by engine in config |
|
Done | Unassigned |
2.
|
Add Optimize Clustering test pipeline |
|
Done | Unassigned |
3.
|
Clustering section in Technical Guide |
|
Done | Unassigned |
[OPT-1728] I can setup a failover scenario for Optimize
| Link | New: This issue is related to SUPPORT-5129 [ SUPPORT-5129 ] |
| Description |
Original:
*Feature description:*
* given: ** I have several Optimize instances running with the same version which use the same Elasticsearch instance ** Optimize instance A is used to import the data and offers the user interface to create, edit and delete entities (e.g. reports or dashboards) ** Optimize instance B is configured to only offer the user interface and the import is disabled. * when: ** One A is failing or shutdown (e.g. due to maintenaince work) * then: ** I can still use B to create, edit, update or delete entities in Optimize ** The reports are all based on the current state of the data without new data being imported to Optimize * such that: ** The user has the possiblity to always ensure a version of Optimize up and running, so in case one instance fails, the other one can take over. *Hint:* * We should think about how to test that behavior. Since we ensure that multiple Optimize can update reports at the same time. * Make sure that there are no conflicts during the index creation while running * When the import is disabled the status api should return that Optimize is currently not importing * Migration (need clarification if that's really necessary): we need to make sure that during the upgrade the old indexes are still available and the deletion happens after the migration is complete. |
New:
*Feature description:*
* given: ** I have several Optimize instances running with the same version which use the same Elasticsearch instance ** Optimize instance A is used to import the data and offers the user interface to create, edit and delete entities (e.g. reports or dashboards) ** Optimize instance B is configured to only offer the user interface and the import is disabled. * when: ** Optimize instance A is failing or shutdown (e.g. due to maintenaince work) * then: ** I can still use B to create, edit, update or delete entities in Optimize ** The reports are all based on the current state of the data without new data being imported to Optimize * such that: ** The user has the possiblity to always ensure a version of Optimize up and running, so in case one instance fails, the other one can take over. *Hint:* * We should think about how to test that behavior. Since we ensure that multiple Optimize can update reports at the same time. * Make sure that there are no conflicts during the index creation while running * When the import is disabled the status api should return that Optimize is currently not importing * Migration (need clarification if that's really necessary): we need to make sure that during the upgrade the old indexes are still available and the deletion happens after the migration is complete. |
| Labels | Original: SUPPORT next_release | New: SUPPORT current_release next_release |
| Labels | Original: SUPPORT current_release next_release | New: SUPPORT current_release |
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 12489 ] |
| Labels | Original: SUPPORT current_release | New: SUPPORT next_release |
| Assignee | Original: Johannes [ johannes.heinemann ] | New: Sebastian Bathke [ sebastian.bathke ] |
| Component/s | New: documentation [ 13751 ] |
| Description |
Original:
*Feature description:*
* given: ** I have several Optimize instances running with the same version which use the same Elasticsearch instance ** Optimize instance A is used to import the data and offers the user interface to create, edit and delete entities (e.g. reports or dashboards) ** Optimize instance B is configured to only offer the user interface and the import is disabled. * when: ** Optimize instance A is failing or shutdown (e.g. due to maintenaince work) * then: ** I can still use B to create, edit, update or delete entities in Optimize ** The reports are all based on the current state of the data without new data being imported to Optimize * such that: ** The user has the possiblity to always ensure a version of Optimize up and running, so in case one instance fails, the other one can take over. *Hint:* * We should think about how to test that behavior. Since we ensure that multiple Optimize can update reports at the same time. * Make sure that there are no conflicts during the index creation while running * When the import is disabled the status api should return that Optimize is currently not importing * Migration (need clarification if that's really necessary): we need to make sure that during the upgrade the old indexes are still available and the deletion happens after the migration is complete. |
New:
*Feature description:*
* given: ** I have several Optimize instances running with the same version which use the same Elasticsearch instance ** Optimize instance A is used to import the data and offers the user interface to create, edit and delete entities (e.g. reports or dashboards) ** Optimize instance B is configured to only offer the user interface and the import is disabled. * when: ** Optimize instance A is failing or shutdown (e.g. due to maintenaince work) * then: ** I can still use B to create, edit, update or delete entities in Optimize ** The reports are all based on the current state of the data without new data being imported to Optimize * such that: ** The user has the possiblity to always ensure a version of Optimize up and running, so in case one instance fails, the other one can take over. *Hint:* * We should think about how to test that behavior. Since we ensure that multiple Optimize can update reports at the same time. * Make sure that there are no conflicts during the index creation while running * When the import is disabled the status api should return that Optimize is currently not importing * Migration (need clarification if that's really necessary): we need to make sure that during the upgrade the old indexes are still available and the deletion happens after the migration is complete. * It should be documented how the clustering works, what are the use-cases and limitation of it |