You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Luke Cwik (Jira)" <ji...@apache.org> on 2021/10/20 18:53:00 UTC

[jira] [Updated] (BEAM-13084) SpannerReadIT failing due to resource exhaustion

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

Luke Cwik updated BEAM-13084:
-----------------------------
    Description: 
Causing these post commit suites to fail:
https://ci-beam.apache.org/job/beam_PostCommit_Java/8169/
https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV1/804/
https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV2/805/
https://ci-beam.apache.org/job/beam_PostCommit_Python36/4501/
https://ci-beam.apache.org/job/beam_PostCommit_Python37/4415/
https://ci-beam.apache.org/job/beam_PostCommit_Python38/1824/

Java Failure
java.util.concurrent.ExecutionException: com.google.cloud.spanner.SpannerException: RESOURCE_EXHAUSTED: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Unable to create database 'beam-testdb-uxoazru4ljtjmur4p3' because the instance 'projects/apache-beam-testing/instances/beam-test' has already reached the maximum database limit (100). Please delete a database in the instance and try again, or choose a different instance.

Python Failure
ResourceExhausted: 429 Unable to create database 'pybeam-read-50e4918bec074b0' because the instance 'projects/apache-beam-testing/instances/beam-test' has already reached the maximum database limit (100)

It looks like we are generating databases and are leaking them since teardown may not always be running (https://github.com/apache/beam/blob/59f41e59a4833c306333c2f2a10c2f730d53c9e7/sdks/java/io/google-cloud-platform/src/test/java/org/apache/beam/sdk/io/gcp/spanner/SpannerReadIT.java#L234) and (https://github.com/apache/beam/blob/a1abdf1d16cb6c74fd2460e90e89cb3cb7c81308/sdks/python/apache_beam/io/gcp/experimental/spannerio_read_it_test.py#L130)


  was:
Causing these post commit suites to fail:
https://ci-beam.apache.org/job/beam_PostCommit_Java/8169/
https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV1/804/
https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV2/805/

java.util.concurrent.ExecutionException: com.google.cloud.spanner.SpannerException: RESOURCE_EXHAUSTED: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Unable to create database 'beam-testdb-uxoazru4ljtjmur4p3' because the instance 'projects/apache-beam-testing/instances/beam-test' has already reached the maximum database limit (100). Please delete a database in the instance and try again, or choose a different instance.

It looks like we are generating databases and are leaking them since @TearDown may not always be running (https://github.com/apache/beam/blob/59f41e59a4833c306333c2f2a10c2f730d53c9e7/sdks/java/io/google-cloud-platform/src/test/java/org/apache/beam/sdk/io/gcp/spanner/SpannerReadIT.java#L234).


> SpannerReadIT failing due to resource exhaustion
> ------------------------------------------------
>
>                 Key: BEAM-13084
>                 URL: https://issues.apache.org/jira/browse/BEAM-13084
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-gcp
>            Reporter: Luke Cwik
>            Priority: P2
>
> Causing these post commit suites to fail:
> https://ci-beam.apache.org/job/beam_PostCommit_Java/8169/
> https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV1/804/
> https://ci-beam.apache.org/job/beam_PostCommit_Java_DataflowV2/805/
> https://ci-beam.apache.org/job/beam_PostCommit_Python36/4501/
> https://ci-beam.apache.org/job/beam_PostCommit_Python37/4415/
> https://ci-beam.apache.org/job/beam_PostCommit_Python38/1824/
> Java Failure
> java.util.concurrent.ExecutionException: com.google.cloud.spanner.SpannerException: RESOURCE_EXHAUSTED: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Unable to create database 'beam-testdb-uxoazru4ljtjmur4p3' because the instance 'projects/apache-beam-testing/instances/beam-test' has already reached the maximum database limit (100). Please delete a database in the instance and try again, or choose a different instance.
> Python Failure
> ResourceExhausted: 429 Unable to create database 'pybeam-read-50e4918bec074b0' because the instance 'projects/apache-beam-testing/instances/beam-test' has already reached the maximum database limit (100)
> It looks like we are generating databases and are leaking them since teardown may not always be running (https://github.com/apache/beam/blob/59f41e59a4833c306333c2f2a10c2f730d53c9e7/sdks/java/io/google-cloud-platform/src/test/java/org/apache/beam/sdk/io/gcp/spanner/SpannerReadIT.java#L234) and (https://github.com/apache/beam/blob/a1abdf1d16cb6c74fd2460e90e89cb3cb7c81308/sdks/python/apache_beam/io/gcp/experimental/spannerio_read_it_test.py#L130)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)