You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 30, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 30, 2026. It is now read-only.
Spanner: gRPC Retry and Timeout Settings should be used from configuration #20
The Java client library for Spanner has been changed to use the gapic client and rely on Gax for almost all retries, so these constants are not used very much anymore. There are two exceptions:
Retrying aborted transactions: This is currently using the SpannerRetryHelper.
The retry settings from gapic are defined for the different gRPC methods. The two exceptions above are not directly related to one method, but could be caused by different methods, so there is no direct choice for which retry setting from the config that should be used. My suggestion would be:
The Java client library for Spanner has been changed to use the gapic client and rely on Gax for almost all retries, so these constants are not used very much anymore. There are two exceptions:
Retrying aborted transactions: This is currently using the SpannerRetryHelper.
The retry settings from gapic are defined for the different gRPC methods. The two exceptions above are not directly related to one method, but could be caused by different methods, so there is no direct choice for which retry setting from the config that should be used. My suggestion would be:
Activity
olavloite commentedon Jun 25, 2019
The Java client library for Spanner has been changed to use the gapic client and rely on Gax for almost all retries, so these constants are not used very much anymore. There are two exceptions:
SpannerRetryHelper.The retry settings from gapic are defined for the different gRPC methods. The two exceptions above are not directly related to one method, but could be caused by different methods, so there is no direct choice for which retry setting from the config that should be used. My suggestion would be:
@kolea2 and @crwilcox Do you both agree with that?
skuruppu commentedon Jan 9, 2020
I think this is reasonable @olavloite. Please go ahead with making the necessary changes.
olavloite commentedon Feb 28, 2020
All custom retry values have now been replaced by values from the gapic configuration by #48 and #49.