[
https://issues.apache.org/jira/browse/GOBBLIN-1831?focusedWorklogId=861588&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861588
]
ASF GitHub Bot logged work on GOBBLIN-1831:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/May/23 16:57
Start Date: 11/May/23 16:57
Worklog Time Spent: 10m
Work Description: Will-Lo merged PR #3694:
URL: https://github.com/apache/gobblin/pull/3694
Issue Time Tracking
-------------------
Worklog Id: (was: 861588)
Time Spent: 40m (was: 0.5h)
> Use Flow Execution ID in Gobblin cluster cancellation semantics and jobname
> IDs if possible
> -------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-1831
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1831
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: William Lo
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When executing jobs from GaaS to Gobblin cluster, there can be a mismatch of
> flowexecution ids to jobs running on Gobblin cluster.
> To address this, we tried adding the FlowExecutionId to the jobSpec, but that
> meant that jobs could run concurrently on Gobblin cluster when they should
> have been deduped.
> So instead, during cancellation, we want to check if the incoming spec has a
> flow execution ID. If so, then it will cancel the existing job only if the
> flow execution IDs match. Otherwise, it will know that the current job does
> not match the incoming request and should not be deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
