[
https://issues.apache.org/jira/browse/GOBBLIN-1702?focusedWorklogId=807260&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-807260
]
ASF GitHub Bot logged work on GOBBLIN-1702:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Sep/22 05:09
Start Date: 09/Sep/22 05:09
Worklog Time Spent: 10m
Work Description: hanghangliu commented on code in PR #3556:
URL: https://github.com/apache/gobblin/pull/3556#discussion_r966630964
##########
gobblin-cluster/src/main/java/org/apache/gobblin/cluster/HelixUtils.java:
##########
@@ -278,13 +278,16 @@ static void waitJobCompletion(HelixManager helixManager,
String workFlowName, St
case STOPPING:
log.info("Waiting for job {} to complete... State - {}", jobName,
jobState);
Thread.sleep(TimeUnit.SECONDS.toMillis(1L));
+ if (stoppingStateEndTime == null) {
+ stoppingStateEndTime = jobStartTimeMillis +
stoppingStateTimeoutInSeconds * 1000;
Review Comment:
Done.
Log can be traced by line 279 if the job is STOPPING state.
Issue Time Tracking
-------------------
Worklog Id: (was: 807260)
Time Spent: 1.5h (was: 1h 20m)
> Fix Bug when wait and checking helix job state till completion
> --------------------------------------------------------------
>
> Key: GOBBLIN-1702
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1702
> Project: Apache Gobblin
> Issue Type: Bug
> Components: gobblin-cluster
> Reporter: Hanghang Liu
> Assignee: Hung Tran
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently the HelixUtils.waitJobCompletion() has a bug when hob in STOPPING
> state, it immediately try to delete it, instead of waiting the job itself to
> transit to STOPPED state, due to the stoppingStateEndTime is not set
> correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
