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

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

                Author: ASF GitHub Bot
            Created on: 30/Jun/22 10:25
            Start Date: 30/Jun/22 10:25
    Worklog Time Spent: 10m 
      Work Description: phet commented on code in PR #3516:
URL: https://github.com/apache/gobblin/pull/3516#discussion_r910862461


##########
gobblin-service/src/main/java/org/apache/gobblin/service/modules/scheduler/GobblinServiceJobScheduler.java:
##########
@@ -322,6 +326,19 @@ public AddSpecResponse onAddSpec(Spec addedSpec) {
       return new AddSpecResponse<>(response);
     }
 
+    // Check quota limits against run immediately flows or adhoc flows before 
saving the schedule
+    if (!jobConfig.containsKey(ConfigurationKeys.JOB_SCHEDULE_KEY) || 
PropertiesUtils.getPropAsBoolean(jobConfig, 
ConfigurationKeys.FLOW_RUN_IMMEDIATELY, "false")) {

Review Comment:
   it feels potentially confusing that the flow would not be scheduled at all 
(for the future) just because the quota is exceeded now.  wouldn't it be safe 
to `scheduleJob` anyway (even if we don't believe the first, runImmediately 
execution would succeed)?





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

    Worklog Id:     (was: 786508)
    Time Spent: 4h 50m  (was: 4h 40m)

> Return different Http Status on GaaS if Quota is Exceeded
> ---------------------------------------------------------
>
>                 Key: GOBBLIN-1656
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1656
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-service
>            Reporter: William Lo
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 4h 50m
>  Remaining Estimate: 0h
>
> GaaS has quota limits for proxy users and flowGroups.
> When a user wants to create a flow that exceeds their specified quota, the 
> flow should
> 1) Not be run
> 2) Return a http status code (i.e. 503) due to exceeding the resource. This 
> allows clients to implement some wait and retry functionality



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

Reply via email to