[
https://issues.apache.org/jira/browse/GOBBLIN-1916?focusedWorklogId=881201&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-881201
]
ASF GitHub Bot logged work on GOBBLIN-1916:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Sep/23 16:42
Start Date: 21/Sep/23 16:42
Worklog Time Spent: 10m
Work Description: Will-Lo commented on PR #3783:
URL: https://github.com/apache/gobblin/pull/3783#issuecomment-1729936183
What would the behavior be when there are concurrent flows with the same
flow group and flow name? Is there a hard line not to support this behavior?
Issue Time Tracking
-------------------
Worklog Id: (was: 881201)
Time Spent: 20m (was: 10m)
> Remove flowExecutionId from Multi-Active Lease Arbitration
> ----------------------------------------------------------
>
> Key: GOBBLIN-1916
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1916
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-service
> Reporter: Urmi Mustafi
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Including flow execution id as a part of multi-active lease arbitration for
> LAUNCH events is frequently causing the same trigger on multiple hosts to be
> perceived as unique flow executions since the flow execution id reflects the
> system clock of the participant. For a single flow trigger, there may be up
> to N number of flow execution ids where N is the number of active
> participants. The same flow action is perceived as unique from the other ones
> and excess flows are launched concurrently (upon which the additional ones
> are cancelled). Remove all use of the flow execution id for the LAUNCH case
> right now. In the future, we will generalize the arbiter for other flow
> actions when we determine the value they will require for arbitration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
