Urmi Mustafi created GOBBLIN-1948:
-------------------------------------
Summary: Use Consist flowExecutionId Across Participants
Key: GOBBLIN-1948
URL: https://issues.apache.org/jira/browse/GOBBLIN-1948
Project: Apache Gobblin
Issue Type: New Feature
Components: gobblin-service
Reporter: Urmi Mustafi
Assignee: Abhishek Tiwari
A consistent flowExecutionId is used during lease arbitration between hosts and
that id is available to the DagActionStoreChangeMonitor but not used when
passing launch events to the Orchestrator for recompilation and eventual
execution. The unintended consequence of this is that a different
flowExecutionId will be used across each participant when the flow is
recompiled before passing to the DagManager. This messes up the job status of
the most recent flow execution of each flow as it appears there are N flow
execution Ids, 1 for each of the N hosts. Only one will be executed but the
other N-1 are stuck in "compiling" job status state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
