Bug #93737 mysqlbinlog mermory used grows unstoped
Submitted: 26 Dec 2018 1:57 Modified: 12 Mar 2019 14:58
Reporter: chandler bong Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: Command-line Clients Severity:S2 (Serious)
Version:5.6 OS:Any
Assigned to: CPU Architecture:Any

[26 Dec 2018 1:57] chandler bong
This bug happens when the server contains many tables.When the amount of all the tables is bigger than the number the option table_definition_cache defined, even same table will have different table_id.table_id is used in binlog table map event.The client mysqlbinlog will put table_map_event in a hash table.And the key is table id.Since table id will grow unstoppedly, the size of the hash table grows unstoppedly.When we used option --stop-never, the usage of mysqlbinlog will group bigger and bigger.

How to repeat:
set table_definition_cache less than the then amount of active tables

Suggested fix:
mysqlbinlog should contains a hash table, which records the table_id of tables.One table shold only contains one table_id.When table_id is new for a table,we can delete old table_map_event to avoid the memory grows unreasonably.
[11 Feb 2019 14:09] MySQL Verification Team

What are the values for the following variables:

* table_definition_cache
* table_open_cache
* table_open_cache_instances
[12 Mar 2019 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".