Cannot resolve Durable Object due to transient issue on remote node.
We've gotten a ton of errors lately due to
Cannot resolve Durable Object due to transient issue on remote node.
What do you suggest we do about it?
we're really sensitive about latency, so adding exponential backoffs is not ideal.5 Replies
Hi, This error can occur due to (1) transient health issues in Durable Objects infrastructure or (2) too much load to a single object. For scenario (1), you can cross reference error timestamps with Durable Objects Incident History - https://www.cloudflarestatus.com/history.
These are retryable errors and it is recommended to retry with backoff.
Is there any public information about load limits per object?
How far should I be able to push them in terms of RPS?
There’s no hard limit on a single Durable Object. However, by design, a single Durable Object is a single-threaded coordinator - https://developers.cloudflare.com/durable-objects/platform/limits/#how-much-work-can-a-single-durable-object-do.
Requests per second (RPS) will depend on application logic. Typically, we see 1K RPS with some minimal Storage API operations or compute (data serialization, etc). With just WebSocket message fan out/fan in and no storage, we’ve seen 2K+ RPS. With If a single Durable Object is overloaded, you will see these errors - https://developers.cloudflare.com/durable-objects/reference/troubleshooting/#durable-object-is-overloaded
Cloudflare Docs
Limits · Cloudflare Durable Objects docs
Durable Objects are only available on the Workers Paid plan.
Cloudflare Docs
Troubleshooting · Cloudflare Durable Objects docs
wrangler dev and wrangler tail are both available to help you debug your Durable Objects.
FYI correction to my answer above about
transient issue errors
Hope this helps, I would also encourage joining #durable-objects since there are other folks there who can help with DO questionsawesome, thank you