We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5871

Optimize update should fail if reading the metadata version fails

    • Icon: Bug Report Bug Report
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.6.6, 3.7.0
    • None
    • backend
    • None
    • Not defined

      Context:
      We recently observed cluster updates that missed to run the update in case there was a problem reading the metadata version. This behavior was initially intended to gracefully handle the case that there is no existing schema present and to skip the update execution in such cases. However in this case there was a schema present but probably not yet readable (as elastic was just updated as well it's likely that the indices were still in a recovery state) and when trying to retrieve the metadata document from elastic an exception occurred. Still the update was skipped and thus missed.

      AT:

      • In case of a failure reading the metadata document from the index the update should fail hard instead of silently succeeding to get retried eventually
      • In case of no metadata index or document present the update should get skipped without failure

        This is the controller panel for Smart Panels app

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

            Optimize update should fail if reading the metadata version fails

              • Icon: Bug Report Bug Report
              • Resolution: Done
              • Icon: L3 - Default L3 - Default
              • 3.6.6, 3.7.0
              • None
              • backend
              • None
              • Not defined

                Context:
                We recently observed cluster updates that missed to run the update in case there was a problem reading the metadata version. This behavior was initially intended to gracefully handle the case that there is no existing schema present and to skip the update execution in such cases. However in this case there was a schema present but probably not yet readable (as elastic was just updated as well it's likely that the indices were still in a recovery state) and when trying to retrieve the metadata document from elastic an exception occurred. Still the update was skipped and thus missed.

                AT:

                • In case of a failure reading the metadata document from the index the update should fail hard instead of silently succeeding to get retried eventually
                • In case of no metadata index or document present the update should get skipped without failure

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        sebastian.bathke Sebastian Bathke
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              sebastian.bathke Sebastian Bathke
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated:
                                Resolved: