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

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

                Author: ASF GitHub Bot
            Created on: 14/Sep/22 00:59
            Start Date: 14/Sep/22 00:59
    Worklog Time Spent: 10m 
      Work Description: umustafi commented on code in PR #3557:
URL: https://github.com/apache/gobblin/pull/3557#discussion_r970200988


##########
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:
   I see that is a reasonable name then. We will use this to keep all or any 
hosts up to date with leader who is accepting all the API requests in warm 
standby mode. Only leader node will be able to execute. Changing to use 
`warmStandbyEnabled` key.





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

    Worklog Id:     (was: 808484)
    Time Spent: 1h 20m  (was: 1h 10m)

> 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 20m
>  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