You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Mikhail Gryzykhin (JIRA)" <ji...@apache.org> on 2018/08/10 18:12:00 UTC
[jira] [Updated] (BEAM-5053) CreateRequestsPerMinutePerUser quota
limit exceeded
[ https://issues.apache.org/jira/browse/BEAM-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Gryzykhin updated BEAM-5053:
------------------------------------
Priority: Minor (was: Major)
> CreateRequestsPerMinutePerUser quota limit exceeded
> ---------------------------------------------------
>
> Key: BEAM-5053
> URL: https://issues.apache.org/jira/browse/BEAM-5053
> Project: Beam
> Issue Type: Bug
> Components: test-failures, testing
> Reporter: Mikhail Gryzykhin
> Assignee: Mikhail Gryzykhin
> Priority: Minor
> Time Spent: 1h
> Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/553/consoleFull]
>
> Dataflow has a CreateRequestsPerMinutePerUser quota that is 60 requests per minute.
> Our Java Validate Runner tests spin up more than 250 jobs in a run.
> We should look into best way to fix the issue. Currently, I see following options:
> # Add retry logic. Although this limits us to 1 dataflow job start per second for whole Jenkins. In long scale this can also block one test job if other jobs take all the slots.
> # Utilize different users to spin Dataflow jobs.
> # Find way to rise quota limit on Dataflow. By default the field limits value to 60 requests per minute.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)