Resource starvation at low message volumes

spotify / async-google-pubsub-client

[SUNSET] Async Google Pubsub Client

Apache License 2.0

158 stars 40 forks source link

Resource starvation at low message volumes #14

Closed negz closed 8 years ago

negz commented 8 years ago

We've run into a bug where this client starves itself on resources. The puller threads never gives the acker thread a chance to run and vice versa. We've worked around it by setting the concurrency to 1. This only seems to be an issue when message throughput is very low.

I'm reporting this issue secondhand - I believe @lndbrg discovered it.

negz commented 8 years ago

(I've mostly raised this issue for informational purposes, so other's don't have to find out by word of mouth as I did.)

robertsutherland commented 8 years ago

@negz I have run into this issue even with the concurrency set to 1. Are there any other workarounds that guarantee message acknowledgement?

negz commented 8 years ago

@robertsutherland I'm afraid I don't know of any.

I believe we're moving away from this library internally in favour of Google's new gRPC Pubsub client.

i-maravic commented 8 years ago

Fixed by #21

Released version 1.25 contains the fix.