[jira] [Work logged] (GOBBLIN-1837) Implement multi-active, non blocking for leader host

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

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


##########
gobblin-api/src/main/java/org/apache/gobblin/configuration/ConfigurationKeys.java:
##########
@@ -95,6 +95,24 @@ public class ConfigurationKeys {
   public static final int DEFAULT_LOAD_SPEC_BATCH_SIZE = 500;
   public static final String SKIP_SCHEDULING_FLOWS_AFTER_NUM_DAYS = "skip.scheduling.flows.after.num.days";
   public static final int DEFAULT_NUM_DAYS_TO_SKIP_AFTER = 365;
+  // Scheduler lease determination store configuration
+  // TODO: multiActiveScheduler change here update values for the following keys and rename to more meaningful
+  public static final String SCHEDULER_LEASE_DETERMINATION_STORE_DB_JDBC_DRIVER_KEY = "state.store.db.jdbc.driver";
+  public static final String DEFAULT_SCHEDULER_LEASE_DETERMINATION_STORE_DB_JDBC_DRIVER = "com.mysql.cj.jdbc.Driver";

Review Comment:
   Yes, we can actually reuse the state store configs above. I will remove these keys





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

    Worklog Id:     (was: 863160)
    Time Spent: 6h  (was: 5h 50m)

> 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: 6h
>  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)