tree edd3d0af1af29bc18b9b210f126db3e9eaa6aa67
parent 3cd5a7b23d813d773f5f5463a6847f104bded009
author Jean de Klerk <deklerk@google.com> 1543887132 -0800
committer Jean de Klerk <deklerk@google.com> 1544133546 +0000

pubsub: Receive does not retry ResourceExhausted errors

The reasoning here is that StreamingPull should be a long-lived RPC. If a user
is seeing ResourceExhausted from StreamingPull, it's likely to be something
that they want to act on (increase quota, not over-deploy, etc).

As part of this CL, retrying in pubsub gets re-wired to use the gax.Retryer
pattern. This allows us to pass call options to call, which means that for
the streamingPull call we can pass a custom retryer that does not retry
ResourceExhausted.

As part of this CL, pstest's GServer is exposed. This makes it easier to
create fakes with slightly different semantics, which is a bit more scalable
long-term than exposing knobs for everything testers might want to do.

Fixes #1166

Change-Id: I2073607bcae410e49b0d139859d9b7c48e065a3c
Reviewed-on: https://code-review.googlesource.com/c/36050
Reviewed-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Eno Compton <enocom@google.com>