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
- One to many 2 way, console UI not correc...
Hey, seems I'm facing the exactly same issue with this one: https://github.com/appwrite/appwrite/issues/6016 Since this Github issue stay open for so long, let ...
- Scheduled works locking the entire Maria...
I have a scheduled function and apparently that or something is locking the entire MariaDB database and Appwrite is giving MariaDB errors. This error persists e...
- Need help to create a wrapper which let ...
I’m looking for help setting up Appwrite properly on a VPS so I can build a self-hosting wrapper around it. The goal is to provide a Linux executable that allow...