@TigersWay Retry is definitely
@TigersWay Retry is definitely recommended but I'd like to understand more about your workload when you see these errors? Are these long-running queries?
5 Replies
Thank you @Vy for that question!
There's 3 potential requests in this workload which is supposed to record a website visitors:
- the first one and only one when it happens, is a simple insert (in case of bot),
- the second is a heavy insert with 24 fields (details of the visitor)
- the third is a simple insert again to log errors on the second one
That second one is the one in trouble, but nothing except the size of data (url, path, user-agent,etc) is exceptional.
for the second query, how many rows written?
1 row only
No idea if you can have a look, but the "running" DB is e8ac20f5-28db-408a-8f7c-04e6bf7368fe
Views is the "big" one, "logs" is where I log errors
Bump
confirming you're seeing the same errors with the second query?
@Vy All errors I could catch are on the second query, yes.
I have the details logged in another D1 table in json mode which allow me to say there is nothing special in these queries, so... D1 is working just VERY slow sometimes maybe?