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

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

                Author: ASF GitHub Bot
            Created on: 09/Sep/22 20:13
            Start Date: 09/Sep/22 20:13
    Worklog Time Spent: 10m 
      Work Description: ZihanLi58 commented on code in PR #3557:
URL: https://github.com/apache/gobblin/pull/3557#discussion_r967431494


##########
gobblin-service/src/main/java/org/apache/gobblin/service/modules/core/GobblinServiceConfiguration.java:
##########
@@ -70,6 +70,9 @@ public class GobblinServiceConfiguration {
   @Getter
   private final boolean isHelixManagerEnabled;
 
+  @Getter
+  private final boolean isSpecStoreChangeMonitorEnabled;

Review Comment:
   Multi leaders is more about partitioning that each host can handle part of 
the work. All the features we are doing here are for warm standby so that when 
one leader is down, other hosts can take over the job without gap. That's why I 
use the warm standby as the config name, let me know if you have other thoughts.





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

    Worklog Id:     (was: 807589)
    Time Spent: 1h  (was: 50m)

> New Consumer service that processes changes to Flow Spec Store
> --------------------------------------------------------------
>
>                 Key: GOBBLIN-1705
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1705
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-service
>            Reporter: Urmi Mustafi
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> In the multi-leader version of GaaS, the REST API layer will not directly 
> contact the `GobblinServiceJobScheduler` to respond to API requests. Instead 
> after flow level updates are persisted to MySQL, this new monitor will 
> subscribe to Kafka events informing it of Flow Spec changes corresponding to 
> the API requests and trigger their execution. There will be a similar change 
> to follow to respond to other API requests. 



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

Reply via email to