Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-6693

Adjust onboarding importer to run after application has started

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.10.0-alpha4, 3.10.0
    • None
    • backend
    • None
    • Not defined

      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

        This is the controller panel for Smart Panels app

            [OPT-6693] Adjust onboarding importer to run after application has started

            Helene Waechtler created issue -
            Helene Waechtler made changes -
            Link New: This issue is related to OPT-6223 [ OPT-6223 ]
            Helene Waechtler made changes -
            Link New: This issue is related to OPT-6691 [ OPT-6691 ]
            Helene Waechtler made changes -
            Status Original: Triage [ 10612 ] New: Ready [ 10005 ]
            Helene Waechtler made changes -
            Status Original: Ready [ 10005 ] New: In Development [ 10312 ]
            Helene Waechtler made changes -
            Status Original: In Development [ 10312 ] New: Ready [ 10005 ]
            Helene Waechtler made changes -
            Status Original: Ready [ 10005 ] New: In Development [ 10312 ]
            Helene Waechtler made changes -
            Description Original: *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             		New: *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 and confirm in the logs that the onboarding importer runs after the application was started, not during.
            Helene Waechtler made changes -
            Assignee Original: Helene Waechtler [ helene.waechtler ] New: Joshua Windels [ joshua.windels ]
            Status Original: In Development [ 10312 ] New: In Review [ 10212 ]
            Joshua Windels made changes -
            Assignee Original: Joshua Windels [ joshua.windels ] New: Helene Waechtler [ helene.waechtler ]
            Status Original: In Review [ 10212 ] New: Rework [ 11413 ]

              Unassigned Unassigned
              helene.waechtler Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: