[ 
https://issues.apache.org/jira/browse/GOBBLIN-1840?focusedWorklogId=867875&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-867875
 ]

ASF GitHub Bot logged work on GOBBLIN-1840:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Jun/23 21:31
            Start Date: 27/Jun/23 21:31
    Worklog Time Spent: 10m 
      Work Description: homatthew commented on code in PR #3704:
URL: https://github.com/apache/gobblin/pull/3704#discussion_r1244382872


##########
gobblin-cluster/src/main/java/org/apache/gobblin/cluster/GobblinHelixJobScheduler.java:
##########
@@ -360,7 +400,7 @@ private void waitForJobCompletion(String jobName) {
   }
 
   @Subscribe
-  public void handleDeleteJobConfigArrival(DeleteJobConfigArrivalEvent 
deleteJobArrival) throws InterruptedException {
+  public synchronized void 
handleDeleteJobConfigArrival(DeleteJobConfigArrivalEvent deleteJobArrival) 
throws InterruptedException {

Review Comment:
   1. Since handleDeleteJobConfigArrival is a completely synchronous method, 
the synchronized method handleUpdateJobConfigArrival would just hold the lock 
while deleting and then proceed to handleNewJobConfigArrival. There would be no 
need to distinguish between the two since @Peiyingy needs to address the race 
condition described in 
https://github.com/apache/gobblin/pull/3704/files#r1243111712 by updating the 
map immediately in the newJobConfigArrival method. 
   
   2. Yeah we don't call explicitly call delete so it's just semantics about 
which is more intuitive behavior if we ever use this in the future. Since this 
is purely hypothetical I don't want to waste effort changing the behavior to 
(1).  I think we should just add a comment describing that deleting a workflow 
with throttling enabled means that the next schedulable time for the workflow 
will remain unchanged and you have to wait out the throttle timeout before 
being able to reschedule





Issue Time Tracking
-------------------

    Worklog Id:     (was: 867875)
    Time Spent: 3h 20m  (was: 3h 10m)

> Helix Job scheduler should not try to replace running workflow if within 
> configured time
> ----------------------------------------------------------------------------------------
>
>                 Key: GOBBLIN-1840
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1840
>             Project: Apache Gobblin
>          Issue Type: Improvement
>            Reporter: Matthew Ho
>            Priority: Major
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>




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

Reply via email to