>From what I've seen so far it seems that the topics are created as parts of
multiple tests, both Java and Python based.
I'm not sure why they wouldn't be deleted properly - the tests I've seen
contain teardown sections. Is it possible that some failed tests return
prematurely before the teardown section is executed?
If so, maybe we need to look into other ways of making sure that resources
are deleted and released after the tests.


On Fri, Feb 14, 2020 at 2:27 PM Ismaël Mejía <ieme...@gmail.com> wrote:

> I noticed today that the Beam Postcommit SQL is broken:
> https://builds.apache.org/job/beam_PostCommit_SQL/4019/
> Digging deeper the log message says:
> io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: Your project has
> exceeded a limit: (type="topics-per-project", current=10000, maximum=10000).
> at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:240)
> at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:221)
> at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:140)
> at
> com.google.pubsub.v1.PublisherGrpc$PublisherBlockingStub.createTopic(PublisherGrpc.java:835)
> Can somebody take a look and remove all the unused topics. Is there any
> reason
> we need 10000 topics for our tests? or is this just a mistake in our code
> that can
> be fixed.
> Thanks,
> Ismaël


Michał Walenia
Polidea <https://www.polidea.com/> | Software Engineer

M: +48 791 432 002 <+48791432002>
E: michal.wale...@polidea.com

Unique Tech
Check out our projects! <https://www.polidea.com/our-work>

Reply via email to