[jira] [Closed] (GOBBLIN-1721) Give option to cancel helix workflow through Delete API to avoid job hanging

["Hanghang Liu (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GOBBLIN-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hanghang Liu closed GOBBLIN-1721.
---------------------------------

> Give option to cancel helix workflow through Delete API to avoid job hanging
> ----------------------------------------------------------------------------
>
>                 Key: GOBBLIN-1721
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1721
>             Project: Apache Gobblin
>          Issue Type: Bug
>          Components: gobblin-cluster
>            Reporter: Hanghang Liu
>            Assignee: Hung Tran
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Currently when we receive a job restart(handleUpdateJobConfigArrival), GobblinHelixJobLauncher will firstly call  helixTaskDriver.waitToStop to stop the workflow, then initiate the new one. We observe the behavior of Helix taking exceptionally long to stop the workflow, making the job state staying in STOPPING status. This will make waitToStop timeout and throw exception all the time, making the new flow never be able to launch.
> We can utilize Delete API in this case since our job is stateless for Helix, to avoid job hanging.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)