You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "William Lo (Jira)" <ji...@apache.org> on 2023/05/09 19:12:00 UTC

[jira] [Created] (GOBBLIN-1831) Use Flow Execution ID in Gobblin cluster cancellation semantics and jobname IDs if possible

William Lo created GOBBLIN-1831:
-----------------------------------

             Summary: 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


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)