You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Urmi Mustafi (Jira)" <ji...@apache.org> on 2023/05/26 20:44:00 UTC
[jira] [Created] (GOBBLIN-1837) Implement multi-active, non blocking for leader host
Urmi Mustafi created GOBBLIN-1837:
-------------------------------------
Summary: 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
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)