High database memory usage after increasing performance_schema_max_digest_length

[kochetovd]

On Friday I reduced the memory for MySQL on all instances by 4GB and deployed the new configs. However, the database crashed in the night because it used up too much memory and the server went OOM. Another one crashed for the same reason the next day.

innodb_change_buffering: changes ### Previous value : changes
innodb_change_buffer_max_size: 20 ### Previous value : 20
innodb_adaptive_flushing_lwm: 25 ### Previous value : 25
innodb_max_dirty_pages_pct: 70.000000 ### Previous value : 70.000000
innodb_autoextend_increment: 48 ### Previous value : 48
thread_stack: 524288 ### Previous value : 524288
innodb_buffer_pool_instances: 47 ### Previous value : 47
innodb_buffer_pool_size: 50465865728 ### Previous value : 50465865728
innodb_page_cleaners: 47 ### Previous value : 47

### Changed ###
innodb_redo_log_capacity: 834666496 ### Previous value : 423624704
innodb_buffer_pool_chunk_size: 134217728 ### Previous value : 67108864
join_buffer_size: 8388608 ### Previous value : 262144
table_open_cache: 2048 ### Previous value : 2000
table_definition_cache: 1792 ### Previous value : 1400
optimizer_search_depth: 0 ### Previous value : 62
thread_pool_size: 12 ### Previous value : 8
performance_schema_max_sql_text_length: 16384 ### Previous value : 1536
max_digest_length: 16384 ### Previous value : 1536
performance_schema_max_digest_length: 16384 ### Previous value : 1536

[kochetovd]

The root cause of the problem is the increased use of performance schema memory related to changes in the values of the max_digest_length, performance_schema_max_digest_length, and performance_schema_max_sql_text_length variables, which Releem does not consider when calculating database memory usage.