camunda / issues

4 stars 0 forks source link

Import of cancelled instances is not blocked when batch operation is absent #743

Closed engineering-issue-sync-app[bot] closed 1 month ago

engineering-issue-sync-app[bot] commented 2 months ago

Description

(This is a follow-up for #5984)

When PROCESS_INSTANCE ELEMENT_TERMINATED record is being imported it searched for corresponding operations and batch operation to update the progress. It may happen that batch operation does not exist (e.g. after data loss). In such case exception is thrown and import is blocked:

io.camunda.operate.exceptions.PersistenceException: org.elasticsearch.action.ActionRequestValidationException: Validation Failed: 1: index is missing;2: index is missing;3: index is missing;4: index is missing;5: index is missing;6: index is missing;7: index is missing;8: index is missing;9: index is missing;10: index is missing;11: index is missing;12: index is missing;13: index is missing;14: index is missing;15: index is missing;16: index is missing;17: index is missing;
    at io.camunda.operate.zeebeimport.AbstractImportBatchProcessor.performImport(AbstractImportBatchProcessor.java:43) ~[operate-importer-common-8.3.3.jar!/:8.3.3]

Mitigation

One solution is to delete operations for which batch operations do not exist anymore. See Support KB

TODO

Additional Information


Acceptance Criteria

Definition of Ready - Checklist

:robot: This issue is automatically synced from: source