Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-12274

Too many connections warning in error log

Details

    Attachments

      Issue Links

        Activity

          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.

          svoj Sergey Vojtovich added a comment - 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.

          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?

          vnsavage Iliya Polihronov added a comment - 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?
          svoj Sergey Vojtovich added a comment - serg ?
          danblack Daniel Black added a comment -

          With TCP health checks like MDEV-21456 this is getting more important to mask off.

          Can you please review pr 2213.

          danblack Daniel Black added a comment - With TCP health checks like MDEV-21456 this is getting more important to mask off. Can you please review pr 2213 .
          danblack Daniel Black added a comment -

          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.

          danblack Daniel Black added a comment - 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.

          People

            TheLinuxJedi Andrew Hutchings (Inactive)
            svoj Sergey Vojtovich
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.