Bug #87390 MySQL service does not release memory after upgrade to 5.7.16
Submitted: 11 Aug 2017 7:44 Modified: 14 Sep 2017 13:38
Reporter: Sik Yin Wong Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.7.16 OS:Red Hat (6.8)
Assigned to: CPU Architecture:Any

[11 Aug 2017 7:44] Sik Yin Wong 
Description:
Before I upgrade the MySQL, it is using 5.6.26 version and memory usage not more than 4GB. After I upgrade to 5.7.16, found the memory keeping high two days later. Sometimes it will use swap memory. The memory usage will drop significantly after I restart the instance. However, the memory usage growth quickly and starts using the swap memory after two days. 

How to repeat:
None

Suggested fix:
None
[14 Aug 2017 13:38] MySQL Verification Team 
Hi!

We have all tested both 5.6 and 5.7 releases and never accounted for the case like yours. In order rto consider whether it is a bug or not we need lots of feedback from you.

Have you changed anything in the 5.7 configuration file ??? Have you starting using some features you have not been using before ??? If you run `ps aux` in the time of swapping what does the report say for the mysql server ??? Have you reduced your memory or added some other programs that are running in parallel ??

Last, but most important, please turn the entire memory instrumentation provided by Performance Schema, and send us a report on all memory usage by each of the modules. We need the full P_S report , before server starts to crash.
[15 Sep 2017 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".