-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Context:
With OPT-3505, Optimize now re-imports running process instances if specific suspension operations have occured. In some cases this is done by re-importing specific instances, but in the case of batch suspension operations all instances have to be re-imported, which is currently achieved by resetting the import index. However, this could lead to a potential race condition as described in the comment here: https://github.com/camunda/camunda-optimize/pull/2074#discussion_r435817458.
To avoid this race condition, we need a way to clear the queue of the running instance import before resetting the index timestamps.
AT:
- The above described race condition is avoided by resetting any potential current import jobs before resetting the import index
This is the controller panel for Smart Panels app
Avoid race condition when resetting running instance import index
-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Context:
With OPT-3505, Optimize now re-imports running process instances if specific suspension operations have occured. In some cases this is done by re-importing specific instances, but in the case of batch suspension operations all instances have to be re-imported, which is currently achieved by resetting the import index. However, this could lead to a potential race condition as described in the comment here: https://github.com/camunda/camunda-optimize/pull/2074#discussion_r435817458.
To avoid this race condition, we need a way to clear the queue of the running instance import before resetting the index timestamps.
AT:
- The above described race condition is avoided by resetting any potential current import jobs before resetting the import index
This is the controller panel for Smart Panels app
- depends on
-
OPT-3505 Suspend state is not imported via userOperationsLog
- Done