#alexanderg-network-retries
mellow stone
what if it times out but in the end succeeds
or what if it succeeds in Stripe and on the return trip we do not get the response due to network issue
So I am talking about a situation where Stripe call 1 succeeded in Stripe but we still initiate a retry due to some failure.
grizzled elbow
gotcha, yeah in that case it could lead to multiple charges yes
mellow stone
Great, thank you!
One more question - can I configure retry strategy and if not what is the default strategy, eg timeout, backoff, etc...
ivory spire
If you're just using a client library and setting the max network retries it uses exponential backoff: https://stripe.com/docs/error-handling#network-errors
There's not a way to configure the retry strategy to something else
mellow stone
Yes, I am just wondering what are the default timeouts (e.g., 1ms or 1s and back off multiplyer), we need this to set timeouts on upstream calls.
ivory spire
Ok one moment
This is where the retry settings are defined in our java library: https://github.com/stripe/stripe-java/blob/ecb791f567f85377f60b272eb9f7a4d91bfb67b7/src/main/java/com/stripe/net/HttpClient.java#L16
Delay starts at 500 milliseconds and goes to a max of 5 seconds
mellow stone
Great, thank you!
ivory spire
No problem!