[MDEV-12274] Too many connections warning in error log Created: 2017-03-15 Updated: 2023-03-07 Resolved: 2022-11-18 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Fix Version/s: | 10.11.2, 10.3.38, 10.4.28, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3 |
| Type: | Task | Priority: | Major |
| Reporter: | Sergey Vojtovich | Assignee: | Andrew Hutchings |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Apply https://github.com/percona/percona-server/commit/7c02b173a27212d7bee1fb2a6e17b746c48a2cf0 |
| Comments |
| Comment by Sergey Vojtovich [ 2017-06-15 ] |
|
Apparently we have this feature since 5.2.9, introduced by this change: https://github.com/MariaDB/server/commit/b08627f93 It requires log_warnings > 3. |
| Comment by Iliya Polihronov [ 2017-06-27 ] |
|
The log_warnings > 4 setting does indeed print the "Too many connections" errors. However, unfortunately such a high setting also prints a lot of other things - like details on every single connection. It's not ideal for a production setup to log all the additional details, while it is very useful to have the "Too many connections" errors. Do you think it is possible that this can be brought to level 1? |
| Comment by Sergey Vojtovich [ 2017-06-28 ] |
|
serg ? |
| Comment by Daniel Black [ 2022-07-30 ] |
|
With TCP health checks like Can you please review pr 2213. |
| Comment by Daniel Black [ 2022-07-30 ] |
|
I'm targetting 10.3 with the aim to implement a uniform tcp based healthcheck/liveniness check within the MariaDB container image without just creating lots of noise in MariaDB's default configuration. The aim also is to keep the MariaDB container image with as standard defaults as the server. |