Robert Nagy
Robert Nagy
Isn't the idea that the sql cache should work cross process? We should probably handle errors like these?
I think this specific error can probably be ignored... though I'm not sure how/when this can otherwise also occur? I'm still confused by this error in general. I thought sqlite...
> However, this shouldn't really be possible with how we are using SQLite in the cache store. Question is how I manage to trigger this then :D. It was in...
I'm getting a lot of these errors in production.
It's usually `#findValue` or `get size()` ``` Error: database is locked at get size (file:///usr/src/app/node_modules/@nxtedition/nxt-undici/lib/sqlite-cache-store.js:298:47) at #prune (file:///usr/src/app/node_modules/@nxtedition/nxt-undici/lib/sqlite-cache-store.js:270:14) at SqliteCacheStore.set (file:///usr/src/app/node_modules/@nxtedition/nxt-undici/lib/sqlite-cache-store.js:238:16) -- ```
I suspect our pruning logic is causing contention which makes sqlite timeout certain queries which leads to "database is locked" errors. I'm going to avoid using `maxEntryCount` in production.
I don't have any good ideas unfortunately. We've added a max entry age option to our cache interceptor (i.e. make sure deleteAt is always withing a week or so) and...
So from what I've understood this is normal behavior and we should either yield and try again or just ignore the error. I would recommend the latter. We can reduce...
@nodejs/streams @mcollina