[
https://issues.apache.org/jira/browse/GOBBLIN-2062?focusedWorklogId=923042&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-923042
]
ASF GitHub Bot logged work on GOBBLIN-2062:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Jun/24 22:04
Start Date: 11/Jun/24 22:04
Worklog Time Spent: 10m
Work Description: arjun4084346 closed pull request #3944: [GOBBLIN-2062]
Ensure the `Orchestrator` always has `DagManager` remove `FlowSpec` - even when
orchestration has failed
URL: https://github.com/apache/gobblin/pull/3944
Issue Time Tracking
-------------------
Worklog Id: (was: 923042)
Time Spent: 5h 10m (was: 5h)
> adhoc flow failure due to concurrent execs must be removed from flow catalog
> ----------------------------------------------------------------------------
>
> Key: GOBBLIN-2062
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2062
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-service
> Reporter: Kip Kohn
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> the Orchestrator + DagManager MUST remove adhoc flows that violate concurrent
> execs from the flow catalog. otherwise gaas will continue to return '409
> Conflict' to each subsequent attempt to create an adhoc flow with the same
> flowGroup+flowName. this is despite the fact that the flow (which still
> remains in the FlowCatalog, when it shouldn't be) already has the status
> FAILED, which is a "final status".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
