After our production release we have a problem handling big traffic logs from appwrite container:
TypeScript
[Error] Timestamp: 2023-10-10T08:04:18+00:00
[Error] Method: GET
[Error] URL: /v1/databases/:databaseId/collections/:collectionId/documents/:documentId
[Error] Type: PDOException
[Error] Message: SQLSTATE[HY000] [1040] Too many connections
[Error] File: /usr/src/code/app/init.php
[Error] Line: 700
[Error] Timestamp: 2023-10-10T08:04:19+00:00
[Error] Method: GET
[Error] URL: /v1/databases/:databaseId/collections/:collectionId/documents
[Error] Type: PDOException
[Error] Message: SQLSTATE[HY000] [1040] Too many connections
[Error] File: /usr/src/code/app/init.php
[Error] Line: 700
[Error] Timestamp: 2023-10-10T08:04:19+00:00
TL;DR
The support thread discusses an error message: "SQLSTATE[HY000] [1040] Too many connections" that occurs when handling big traffic logs from the Appwrite container. The user considers passing the variables through compose variables or adding them to the .env file. They also mention four variables to try fiddling around with: _APP_CONNECTIONS_MAX, _APP_POOL_CLIENTS, _APP_SERVER_MULTIPROCESS, and _APP_WORKER_PER_CORE, with a corresponding GitHub link. Unfortunately, no solution is provided in the thread.You can try fiddling around with:
- _APP_CONNECTIONS_MAX
- _APP_POOL_CLIENTS
- _APP_SERVER_MULTIPROCESS
- _APP_WORKER_PER_CORE
these are not present in documentation - should I just put them into .env file?
nvm just pass them through compose variables
Recommended threads
- Free plan Usage
I using a free plan with one organization. I have three projects but on the free plan I should be able to have 2 projects running But in my case only 1 out of ...
- Database AI Column Suggestion Use Case
I tried using the AI column suggestion feature. For me, I prefer writing my column design separately in a notepad. Then my intention is to paste it into the AI ...
- Cant get realtime working
Hey I nned some help with realtime a gain. I was using client.subscribe(...), and i found out that its depricated then i believe realtime.subscribe(...) is the ...