[
https://issues.apache.org/jira/browse/GOBBLIN-1916?focusedWorklogId=881202&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-881202
]
ASF GitHub Bot logged work on GOBBLIN-1916:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Sep/23 16:45
Start Date: 21/Sep/23 16:45
Worklog Time Spent: 10m
Work Description: umustafi commented on PR #3783:
URL: https://github.com/apache/gobblin/pull/3783#issuecomment-1729941924
> 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?
Good question, this will still allow concurrent flow actions with the same
flow group and flow name. We consolidate flow launches that are within
`epsilon` as they are not considered unique, but this doesn't limit multiple
flows from running at same time. If we complete the launch and one flow is
running, we can still launch another.
Issue Time Tracking
-------------------
Worklog Id: (was: 881202)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
