beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Gryzykhin (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (BEAM-5053) CreateRequestsPerMinutePerUser quota limit exceeded
Date Tue, 31 Jul 2018 23:29:00 GMT

     [ https://issues.apache.org/jira/browse/BEAM-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mikhail Gryzykhin reassigned BEAM-5053:
---------------------------------------

    Assignee: Mikhail Gryzykhin  (was: Chamikara Jayalath)

> 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: Major
>
> [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)

Mime
View raw message