[
https://issues.apache.org/jira/browse/GOBBLIN-1507?focusedWorklogId=634836&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-634836
]
ASF GitHub Bot logged work on GOBBLIN-1507:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Aug/21 22:09
Start Date: 05/Aug/21 22:09
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on a change in pull request
#3353:
URL: https://github.com/apache/gobblin/pull/3353#discussion_r683818151
##########
File path:
gobblin-service/src/main/java/org/apache/gobblin/service/modules/scheduler/GobblinServiceJobScheduler.java
##########
@@ -347,6 +343,30 @@ public AddSpecResponse onAddSpec(Spec addedSpec) {
return new AddSpecResponse<>(response);
}
+ /**
+ * Remove a flowSpec from schedule due to another leader being elected
+ * Unlike onDeleteSpec, we want to avoid deleting the flowSpec on the
executor
+ * and we still want to unschedule if we cannot connect to zookeeper as the
current node cannot be the master
+ * @param specURI
+ * @param specVersion
+ */
+ private void unscheduleSpec(URI specURI, String specVersion) {
Review comment:
or call this from inside onDeleteSpec()
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 634836)
Time Spent: 1h 20m (was: 1h 10m)
> GaaS job scheduler removes flowSpecs on unscheduling
> ----------------------------------------------------
>
> Key: GOBBLIN-1507
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1507
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: William Lo
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> When demoted from leader, GaaS removes all flows from orchestrator. We need
> to ensure that fail over events are not disruptive or destructive to
> currently running flows, we only want the new leader node to handle
> scheduling responsibilities from that point forward.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)