Aditya Pratap Singh created GOBBLIN-2102:
--------------------------------------------
Summary: GaaS concurrent flow check does not work for old running
flows
Key: GOBBLIN-2102
URL: https://issues.apache.org/jira/browse/GOBBLIN-2102
Project: Apache Gobblin
Issue Type: Bug
Reporter: Aditya Pratap Singh
There's a bug that causes GaaS multileader to kick off unintended concurrent
flows which happens in the order described below:
# Host A checks the latest flow execution status to ensure the prior flow is
not running, sees that the prior execution is still running.
# Host A fails the flow pending execution as it cannot run concurrent flow,
this emits a FAILED event to GaaS which is ingested by the JobStatusMonitor.
# Host B checks the latest flow execution status, sees the current flow
execution ID which is FAILED (considered a finished flow).
# Host B kicks off the pending flow execution when it shouldn't be.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
