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
Copy file name to clipboardExpand all lines: src/content/docs/d1/observability/debug-d1.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ The following table lists specific instances of `D1_ERROR`.
62
62
|`Internal error in D1 DB storage caused object to be reset.`| An error has caused the D1 database to restart. | Retry the operation. |
63
63
|`Cannot resolve D1 DB due to transient issue on remote node.`| The query cannot reach the Durable Object containing the D1 database. | Retry the operation. |
64
64
|`Can't read from request stream because client disconnected.`| A query request was made (e.g. uploading a SQL query), but the connection was closed during the query was fully executed. | App action: Retry the operation, and ensure the connection stays open. |
65
-
|`D1 DB storage operation exceeded timeout which caused object to be reset.`| A query is trying to write a large amount of information (e.g. GBs), and is taking too long. | App action: Retry the operation, or split the query into smaller shards. |
65
+
|`D1 DB storage operation exceeded timeout which caused object to be reset.`| A query is trying to write a large amount of information (e.g. GBs), and is taking too long. | App action: Optimize the queries (so that each query takes less time), send fewer requests by spreading the load over time, or shard the queries.|
66
66
|`D1 DB is overloaded. Requests queued for too long.`| The requests to the D1 database are queued for too long, either because there are too many requests, or the queued requests are taking too long. | App action: Optimize the queries (so that each query takes less time), send fewer requests by spreading the load over time, or shard the queries. |
67
67
|`D1 DB is overloaded. Too many requests queued.`| The request queue to the D1 database is too long, either because there are too many requests, or the queued requests are taking too long. | App action: Optimize the queries (so that each query takes less time), send fewer requests by spreading the load over time, or shard the queries. |
68
68
|`D1 DB's isolate exceeded its memory limit and was reset.`| A query loaded too much into memory, causing the D1 database to crash. | App action: Optimize the queries (so that each query takes less time), send fewer requests by spreading the load over time, or shard the queries. |
0 commit comments