[
https://issues.apache.org/jira/browse/GOBBLIN-1773?focusedWorklogId=844480&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-844480
]
ASF GitHub Bot logged work on GOBBLIN-1773:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Feb/23 00:22
Start Date: 09/Feb/23 00:22
Worklog Time Spent: 10m
Work Description: umustafi commented on code in PR #3636:
URL: https://github.com/apache/gobblin/pull/3636#discussion_r1100825888
##########
gobblin-service/src/main/java/org/apache/gobblin/service/modules/scheduler/GobblinServiceJobScheduler.java:
##########
@@ -330,8 +330,9 @@ public AddSpecResponse onAddSpec(Spec addedSpec) {
// Check quota limits against run immediately flows or adhoc flows before
saving the schedule
// In warm standby mode, this quota check will happen on restli API layer
when we accept the flow
Review Comment:
I see did not notice the difference in warm standby mode.
Issue Time Tracking
-------------------
Worklog Id: (was: 844480)
Time Spent: 50m (was: 40m)
> Fix bug in quota manager of gobblinservice
> ------------------------------------------
>
> Key: GOBBLIN-1773
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1773
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Zihan Li
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We used to check the quota when we accept flow for ad-hoc flow and run
> immediately flow. But we only use the same execution id for ad-hoc flow. So
> for a run immediately flow, we will check quota once with a random execution
> id, and then really run the job with a different execution id and forget the
> first one. This will cause us to double-check the quota for a run immediately
> flow and never release one of them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
