Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Description
Context:
In some clusters we have observed that Optimize cannot start due to the onboarding data importer encountering issues with ES, presumably due to insufficient ES resources. While ideally the onboarding importer should not encounter those issues, Optimize should still be able to start even if issues occur during onboarding import.
Hence, we should adjust the importer to not run during application start but instead run after Optimize has started. If issues occur this can be logged and looked into separately, but should not crash Optimize.
AT:
- onboarding importer runs after Optimize has started, not during application startup
Testing notes:
Start Optimize in C8SaaS mode and ES unavailable for the import of onboarding data (in the support case this happened due to insufficient resources) and confirm in the logs that the onboarding importer runs after the application was started, not during (ie errors from attempting to write onboarding data should not prevent the application from starting but will occur after startup). See also this comment: https://jira.camunda.com/browse/OPT-6691?focusedCommentId=265946&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-265946
