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

Too many connections warning in error log

Details

    Attachments

      Issue Links

        is duplicated by

        Bug - A problem which impairs or prevents the functions of the product. MDEV-21456 TCP health checks to port 3306 quickly exceed max_connect_errors

        • Major - Major loss of function.
        • Closed
        relates to

        Task - A task that needs to be done. MDEV-24850 Convert log_warnings from numeric level to feature mask

        • Major - Major loss of function.
        • Open

        Activity

          Ascending order - Click to sort in descending order
          svoj Sergey Vojtovich created issue -
          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.

          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.
          svoj Sergey Vojtovich made changes -
          Field Original Value New Value
          Fix Version/s N/A [ 14700 ]
          Fix Version/s 10.1 [ 16100 ]
          Resolution Won't Do [ 10201 ]
          Status Open [ 1 ] Closed [ 6 ]
          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?

          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 ?

          svoj Sergey Vojtovich added a comment - serg ?
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 79994 ] MariaDB v4 [ 133174 ]
          danblack Daniel Black made changes -
          danblack Daniel Black made changes -
          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 made changes -
          Assignee Sergey Vojtovich [ svoj ] Oleksandr Byelkin [ sanja ]
          Resolution Won't Do [ 10201 ]
          Status Closed [ 6 ] Stalled [ 10000 ]
          danblack Daniel Black made changes -
          Assignee Oleksandr Byelkin [ sanja ] Daniel Black [ danblack ]
          danblack Daniel Black made changes -
          Assignee Daniel Black [ danblack ] Oleksandr Byelkin [ sanja ]
          Status Stalled [ 10000 ] In Review [ 10002 ]
          danblack Daniel Black made changes -
          Fix Version/s 10.3 [ 22126 ]
          Fix Version/s N/A [ 14700 ]
          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.
          TheLinuxJedi Andrew Hutchings (Inactive) made changes -
          Assignee Oleksandr Byelkin [ sanja ] Andrew Hutchings [ JIRAUSER52179 ]
          TheLinuxJedi Andrew Hutchings (Inactive) made changes -
          Status In Review [ 10002 ] Stalled [ 10000 ]
          TheLinuxJedi Andrew Hutchings (Inactive) made changes -
          Fix Version/s 10.3.39 [ 28508 ]
          Fix Version/s 10.3 [ 22126 ]
          Resolution Fixed [ 1 ]
          Status Stalled [ 10000 ] Closed [ 6 ]
          danblack Daniel Black made changes -
          Fix Version/s 10.4.28 [ 28509 ]
          Fix Version/s 10.5.19 [ 28511 ]
          Fix Version/s 10.6.12 [ 28513 ]
          Fix Version/s 10.7.8 [ 28515 ]
          Fix Version/s 10.8.7 [ 28517 ]
          Fix Version/s 10.9.5 [ 28519 ]
          Fix Version/s 10.10.3 [ 28521 ]
          Fix Version/s 10.11.2 [ 28523 ]
          serg Sergei Golubchik made changes -
          serg Sergei Golubchik made changes -
          ralf.gebhardt Ralf Gebhardt made changes -
          Fix Version/s 10.3.38 [ 28507 ]
          Fix Version/s 10.3.39 [ 28508 ]

          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.