Uploaded image for project: 'Percona Server'
  1. Percona Server
  2. PS-3430

LP #1580710: Using thread_statistics does not clear state when a thread goes away

    Details

    • Type: Bug
    • Status: Done
    • Priority: Low
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None

      Description

      **Reported in Launchpad by colin last update 19-05-2016 06:19:04

      When running Percona Server 5.6.28-76.1 with thread_statistics=1 and userstat=1, I notice that memory constantly increases with each new connection (from basic calculations, ~400 bytes per connection).
      In our case, applications recycle connections every 10 minutes or after N number of usages. Over time this will result in a large number of connections being used.

      IMO the hash table (global_thread_stats) and the thread_statistics table should both remove the entry for a thread once the thread has died/gone away.

      I reproduced this locally by continuously reconnecting a client and observed the RSS of mysqld.

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                lpjirasync lpjirasync (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: