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

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

                Author: ASF GitHub Bot
            Created on: 31/May/23 05:15
            Start Date: 31/May/23 05:15
    Worklog Time Spent: 10m 
      Work Description: phet commented on code in PR #3700:
URL: https://github.com/apache/gobblin/pull/3700#discussion_r1211098334


##########
gobblin-runtime/src/main/java/org/apache/gobblin/runtime/api/DagActionStore.java:
##########
@@ -70,21 +73,23 @@ public DagAction(String flowGroup, String flowName, String 
flowExecutionId, DagA
    * @param flowGroup flow group for the dag action
    * @param flowName flow name for the dag action
    * @param flowExecutionId flow execution for the dag action
+   * @param dagActionValue the value of the dag action
    * @throws IOException
    * @return true if we successfully delete one record, return false if the 
record does not exist
    */
-  boolean deleteDagAction(String flowGroup, String flowName, String 
flowExecutionId) throws IOException;
+  boolean deleteDagAction(String flowGroup, String flowName, String 
flowExecutionId, DagActionValue dagActionValue) throws IOException;
 
   /***
    * Retrieve action value by the flow group, flow name and flow execution id 
from the {@link DagActionStore}.
    * @param flowGroup flow group for the dag action
    * @param flowName flow name for the dag action
    * @param flowExecutionId flow execution for the dag action
+   * @param dagActionValue the value of the dag action
    * @throws IOException Exception in retrieving the {@link DagAction}.
    * @throws SpecNotFoundException If {@link DagAction} being retrieved is not 
present in store.
    */
-  DagAction getDagAction(String flowGroup, String flowName, String 
flowExecutionId) throws IOException, SpecNotFoundException,
-                                                                               
            SQLException;
+  DagAction getDagAction(String flowGroup, String flowName, String 
flowExecutionId, DagActionValue dagActionValue)

Review Comment:
   for the delete case especially, I wondered whether we'd already have a 
`DagAction` on hand.
   
   overall, and IMO unfortunately, we use quite little abstraction throughout 
gobblin service.  most emblematic is the regular use of `(String, String, 
String)` or `(String, String, long)` to specify a flow execution ID.  an 
alternative impl, by contrast might combine a `FlowExecutionId` w/ a 
`DagActionValue` to form a `DagAction`.  that would be not only more succinct 
and self-documenting, but also more typesafe.  it's from this general 
perspective that I prefer the signature:
   ```
   deleteDagAction(DagAction)
   ```
   to
   ```
   deleteDagAction(String, String, String, DagActionValue)
   ```





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

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

> Implement multi-active, non blocking for leader host
> ----------------------------------------------------
>
>                 Key: GOBBLIN-1837
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1837
>             Project: Apache Gobblin
>          Issue Type: Bug
>          Components: gobblin-service
>            Reporter: Urmi Mustafi
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> This task will include the implementation of non-blocking, multi-active 
> scheduler for each host. It will NOT include metric emission or unit tests 
> for validation. That will be done in a separate follow-up ticket. The work in 
> this ticket includes
>  * define a table to do scheduler lease determination for each flow's trigger 
> event and related methods to execute actions on this tableĀ 
>  * update DagActionStore schema and DagActionStoreMonitor to act upon new 
> "LAUNCH" type events in addition to KILL/RESUME
>  * update scheduler/orchestrator logic to apply the non-blocking algorithm 
> when "multi-active scheduler mode" is enabled, otherwise submit events 
> directly to the DagManager after receiving a scheduler trigger
>  * implement the non-blocking algorithm, particularly handling reminder 
> events if another host is in the process of securing the lease for a 
> particular flow trigger



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

Reply via email to