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

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

                Author: ASF GitHub Bot
            Created on: 13/Sep/23 23:23
            Start Date: 13/Sep/23 23:23
    Worklog Time Spent: 10m 
      Work Description: umustafi commented on code in PR #3771:
URL: https://github.com/apache/gobblin/pull/3771#discussion_r1325143516


##########
gobblin-runtime/src/test/java/org/apache/gobblin/runtime/api/MysqlMultiActiveLeaseArbiterTest.java:
##########
@@ -17,8 +17,10 @@
 
 package org.apache.gobblin.runtime.api;
 
+import com.google.common.base.Optional;

Review Comment:
   I replaced the guava optional with the Java one in the 
`MysqlMultiActiveLeaseArbiter[Test]` but am leaving the other related classes 
as is for now. Will fix going forward.





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

    Worklog Id:     (was: 880273)
    Time Spent: 40m  (was: 0.5h)

> Handle Lease Completion From Other Participants MA Scheduler
> ------------------------------------------------------------
>
>                 Key: GOBBLIN-1907
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1907
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-service
>            Reporter: Urmi Mustafi
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> When other participants complete a lease (not just acquire it) in the time 
> that the current participant has attempted the lease, we will see a NULL 
> lease_acquisition_timestamp and should appropriately handle the resulting 
> value. This case was missed and we were only expecting another participant to 
> have acquired the lease. 
> We also add warning logs for JobExceptions that can be hiding the stack trace 
> of errors encountered in runtime. 



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

Reply via email to