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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: gobblin-cluster
• Assignee: Hung Tran
• Reporter: Hanghang Liu
• Created: 12/Oct/22 18:10
• Updated: 02/Nov/22 04:47
• Resolved: 02/Nov/22 04:47

Description

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.