You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2018/01/10 05:22:00 UTC

[jira] [Resolved] (BEAM-3439) Examples and Dataflow runner tests fail due to quota exceeded

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

Jean-Baptiste Onofré resolved BEAM-3439.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: Not applicable

Removing the jobs stuck for a while helped.

> Examples and Dataflow runner tests fail due to quota exceeded
> -------------------------------------------------------------
>
>                 Key: BEAM-3439
>                 URL: https://issues.apache.org/jira/browse/BEAM-3439
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow, testing
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: Not applicable
>
>
> Jenkins tests are failing due to Dataflow quota exceeded:
> 1. {{Startup of the worker pool in zone us-central1-f failed to bring up any of the desired 1 workers. QUOTA_EXCEEDED: Quota 'DISKS_TOTAL_GB' exceeded.  Limit: 21000.0 in region us-central1.(7a8439dba801f22c): Workflow failed.}}
> 2. {{Project apache-beam-testing has insufficient quota(s) to execute this workflow with 1 instances in region us-central1. Quota summary (required/available): 1/1429 instances, 4/27 CPUs, 430/280 disk GB, 0/1998 SSD disk GB, 1/65 instance groups, 1/15 managed instance groups, 1/41 instance templates, 1/281 in-use IP addresses.}}
> 3. {{Dataflow quota error for jobs-per-project quota. Project apache-beam-testing is running 50 jobs. Please check the quota usage via Pantheon. If it exceeds the limit, please wait for a workflow to finish or contact dataflow-feedback@google.com to request an increase in quota. If it does not, contact dataflow-feedback@google.com.}}
> I think all is related to the disk quota exceeded. I'm investigating why the tests consume so much space.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)