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 Mar 4, 2026. It is now read-only.
I have a set of APIs using this spanner library and as a transfer over a substantial amount of load (a few thousand requests per second) to these APIs I start to get errors from spanner with the following message: 14 UNAVAILABLE: EOF.
Looking around it seems I should simply have to retry this request to have a good chance at succeeding. Curious why this is not a case the library handles for me (I believe I saw some mentions of auto-reties for other transient errors somewhere in the docs). Additionally I would like to better understand what is going on here so I can solve the real underlying issue.
Is this spanner trying to tell me that I need to scale up my cluster in order to provide more reliable throughput? Or is this simply something I should expect to run into from time to time?
Environment details
@google-cloud/spannerversion: v1.4.1Steps to reproduce
Will attempt to create some if needed.
Hello 👋
I have a set of APIs using this spanner library and as a transfer over a substantial amount of load (a few thousand requests per second) to these APIs I start to get errors from spanner with the following message:
14 UNAVAILABLE: EOF.Looking around it seems I should simply have to retry this request to have a good chance at succeeding. Curious why this is not a case the library handles for me (I believe I saw some mentions of auto-reties for other transient errors somewhere in the docs). Additionally I would like to better understand what is going on here so I can solve the real underlying issue.
Is this spanner trying to tell me that I need to scale up my cluster in order to provide more reliable throughput? Or is this simply something I should expect to run into from time to time?