ADECUACIÓN SERVIDOR CENTOS 7

Maracay, 23 de Agosto 2022

Motivo:

Alta carga en el procesador (>60% en 4 núcleos dobles), provocada por el servidor mysql, lo que
ocasiona caída de servicios y pérdida de conexión con el sitio web.

Causa del problema:

Configuración actual de servidor

# For advice on how to change settings please see

# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html

[mysqld]
performance-schema=1
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks

symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
innodb_buffer_pool_size=6828M
max_allowed_packet=268435456
open_files_limit=40000
innodb_file_per_table=1
sort_buffer_size=24M
key_buffer_size=48K
tmp_table_size=316M
innodb_log_file_size=1728M
innodb_buffer_pool_instances=6
max_heap_table_size=316M
query_cache_type=1
max_connections=40
join_buffer_size=24M
query_cache_size=128M
slow_query_log=1
read_rnd_buffer_size=24M
thread_cache_size=128
wait_timeout=120
Verificación con mysqltuner

[root@ns1009683 /]# mysqltuner

>> MySQLTuner 1.9.9
* Jean-Marie Renouard <[email protected]>
* Major Hayden <[email protected]>
>> Bug reports, feature requests, and downloads at http://mysqltuner.pl/
>> Run with '--help' for additional options and output filtering

[--] Skipped version check for MySQLTuner script

[OK] Currently running supported MySQL version 5.7.39-log
[OK] Operating on 64-bit architecture

-------- Log file Recommendations ------------------------------------------------------------------

[OK] Log file /var/log/mysqld.log exists
[--] Log file: /var/log/mysqld.log (1M)
[OK] Log file /var/log/mysqld.log is not empty
[OK] Log file /var/log/mysqld.log is smaller than 32 Mb
[OK] Log file /var/log/mysqld.log is readable.
[!!] /var/log/mysqld.log contains 2380 warning(s).
[!!] /var/log/mysqld.log contains 187 error(s).
[--] 151 start(s) detected in /var/log/mysqld.log
[--] 1) 2022-08-22T16:36:56.481927Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 2) 2022-08-22T15:35:23.882313Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 3) 2022-08-22T05:28:31.859229Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 4) 2022-08-22T05:26:42.058948Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 5) 2022-08-22T05:17:53.389437Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 6) 2022-08-22T05:10:11.716138Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 7) 2022-08-22T05:01:38.513052Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 8) 2022-08-22T04:50:17.866724Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 9) 2022-08-22T01:30:28.483006Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 10) 2022-08-22T01:29:26.001346Z 0 [Note] /usr/sbin/mysqld: ready for connections.
[--] 146 shutdown(s) detected in /var/log/mysqld.log
[--] 1) 2022-08-22T16:34:02.254452Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 2) 2022-08-22T15:35:21.734627Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 3) 2022-08-22T05:28:30.021216Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 4) 2022-08-22T05:26:40.258996Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 5) 2022-08-22T05:17:51.585174Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 6) 2022-08-22T05:10:09.855662Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 7) 2022-08-22T05:01:36.590625Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 8) 2022-08-22T04:50:15.958810Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 9) 2022-08-22T01:30:06.782144Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
[--] 10) 2022-08-22T01:29:24.072346Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

-------- Storage Engine Statistics -----------------------------------------------------------------

[--] Status: +ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MEMORY +MRG_MYISAM
+MyISAM +PERFORMANCE_SCHEMA
[--] Data in InnoDB tables: 1.3G (Tables: 99)
[OK] Total fragmented tables: 0

-------- Analysis Performance Metrics --------------------------------------------------------------

[--] innodb_stats_on_metadata: OFF
[OK] No stat updates during querying INFORMATION_SCHEMA.

-------- Views Metrics -----------------------------------------------------------------------------

-------- Triggers Metrics --------------------------------------------------------------------------

-------- Routines Metrics --------------------------------------------------------------------------

-------- Security Recommendations ------------------------------------------------------------------

[OK] There are no anonymous accounts for any database users
[OK] All database users have passwords assigned
[--] There are 620 basic passwords in the list.

-------- CVE Security Recommendations --------------------------------------------------------------

[OK] NO SECURITY CVE FOUND FOR YOUR VERSION

-------- Performance Metrics -----------------------------------------------------------------------

[--] Up for: 20h 26m 45s (19M q [269.982 qps], 139K conn, TX: 1051G, RX: 36G)
[--] Reads / Writes: 97% / 3%
[--] Binary logging is disabled
[--] Physical Memory : 30.9G
[--] Max MySQL memory : 20.0G
[--] Other process memory: 0B
[--] Total buffers: 7.2G global + 328.4M per thread (40 max threads)
[--] P_S Max memory usage: 72B
[--] Galera GCache Max memory usage: 0B
[OK] Maximum reached memory usage: 9.8G (31.58% of installed RAM)
[OK] Maximum possible memory usage: 20.0G (64.76% of installed RAM)
[OK] Overall possible memory usage with other process is compatible with memory available
[OK] Slow queries: 0% (0/19M)
[OK] Highest usage of available connections: 20% (8/40)
[OK] Aborted connections: 0.01% (20/139161)
[!!] CPanel and Flex system skip-name-resolve should be on
[!!] Query cache may be disabled by default due to mutex contention.
[OK] Query cache efficiency: 73.0% (13M cached / 18M selects)
[!!] Query cache prunes per day: 584736
[OK] Sorts requiring temporary tables: 0% (273 temp sorts / 1M sorts)
[OK] No joins without indexes
[!!] Temporary tables created on disk: 65% (373K on disk / 571K total)
[OK] Thread cache hit rate: 99% (8 created / 139K connections)
[OK] Table cache hit rate: 99% (5M hits / 5M requests)
[OK] table_definition_cache (1400) is greater than number of tables (379)
[OK] Open file limit used: 0% (49/40K)
[OK] Table locks acquired immediately: 100% (2K immediate / 2K locks)

-------- Performance schema ------------------------------------------------------------------------

[--] Performance_schema is activated.
[--] Memory used by P_S: 72B
[--] Sys schema is installed.

-------- ThreadPool Metrics ------------------------------------------------------------------------

[--] ThreadPool stat is disabled.

-------- MyISAM Metrics ----------------------------------------------------------------------------

[!!] Key buffer used: 54.2% (26.0K used / 48.0K cache)
[OK] Key buffer size / total MyISAM indexes: 48.0K/43.0K
[OK] Read Key buffer hit rate: 98.4% (1K cached / 20 reads)

-------- InnoDB Metrics ----------------------------------------------------------------------------

[--] InnoDB is enabled.
[--] InnoDB Thread Concurrency: 0
[OK] InnoDB File per table is activated
[OK] InnoDB buffer pool / data size: 6.8G/1.3G
[!!] Ratio InnoDB log file size / InnoDB Buffer pool size (50%): 1.7G * 2/6.8G should be equal to
25%
[OK] InnoDB buffer pool instances: 6
[--] Number of InnoDB Buffer Pool Chunk: 54 for 6 Buffer Pool Instance(s)
[OK] Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size &
Innodb_buffer_pool_instances
[OK] InnoDB Read buffer efficiency: 100.00% (79008191593 hits/ 79008258975 total)
[!!] InnoDB Write Log efficiency: 70.18% (367338 hits/ 523398 total)
[OK] InnoDB log waits: 0.00% (0 waits / 156060 writes)

-------- Aria Metrics ------------------------------------------------------------------------------

[--] Aria Storage Engine not available.

-------- TokuDB Metrics ----------------------------------------------------------------------------

[--] TokuDB is disabled.

-------- XtraDB Metrics ----------------------------------------------------------------------------

[--] XtraDB is disabled.

-------- Galera Metrics ----------------------------------------------------------------------------

[--] Galera is disabled.

-------- Replication Metrics -----------------------------------------------------------------------

[--] Galera Synchronous replication: NO
[--] No replication slave(s) for this server.
[--] Binlog format: ROW
[--] XA support enabled: ON
[--] Semi synchronous replication Master: Not Activated
[--] Semi synchronous replication Slave: Not Activated
[--] This is a standalone server

-------- Recommendations ---------------------------------------------------------------------------

General recommendations:
Check warning line(s) in /var/log/mysqld.log file
Check error line(s) in /var/log/mysqld.log file
MySQL was started within the last 24 hours - recommendations may be inaccurate
name resolution is enabled due to cPanel doesn't support this disabled.
Increasing the query_cache size over 128M may reduce performance
Temporary table size is already large - reduce result set size
Reduce your SELECT DISTINCT queries without LIMIT clauses
Before changing innodb_log_file_size and/or innodb_log_files_in_group read this:
https://bit.ly/2TcGgtU
Variables to adjust:
skip-name-resolve=0
query_cache_size (=0)
query_cache_type (=0)
query_cache_size (> 128M) [see warning above]
key_buffer_size (~ 26K)
innodb_log_file_size should be (=864M) if possible, so InnoDB total log files size equals 25% of
buffer pool size.
Descomposición de carga asociada a mysql (carga por hilo)
Comando pidstat -t -p <mysqld_pid> 1:

Pidstat –t –p 1945 1

09:26:11 AM UID TGID TID %usr %system %guest %CPU CPU Command
09:26:12 AM 27 1945 - 100.00 2.00 0.00 100.00 4 mysqld
09:26:12 AM 27 - 1945 0.00 0.00 0.00 0.00 4 |__mysqld
09:26:12 AM 27 - 1946 0.00 0.00 0.00 0.00 5 |__mysqld
09:26:12 AM 27 - 1947 0.00 0.00 0.00 0.00 1 |__mysqld
09:26:12 AM 27 - 1948 0.00 0.00 0.00 0.00 7 |__mysqld
09:26:12 AM 27 - 1949 0.00 0.00 0.00 0.00 0 |__mysqld
09:26:12 AM 27 - 1950 0.00 0.00 0.00 0.00 1 |__mysqld
09:26:12 AM 27 - 1951 0.00 0.00 0.00 0.00 1 |__mysqld
09:26:12 AM 27 - 1952 0.00 0.00 0.00 0.00 6 |__mysqld
09:26:12 AM 27 - 1953 0.00 0.00 0.00 0.00 1 |__mysqld
09:26:12 AM 27 - 1954 0.00 0.00 0.00 0.00 2 |__mysqld
09:26:12 AM 27 - 1955 0.00 0.00 0.00 0.00 2 |__mysqld
09:26:12 AM 27 - 1956 0.00 0.00 0.00 0.00 2 |__mysqld
09:26:12 AM 27 - 1957 0.00 0.00 0.00 0.00 7 |__mysqld
09:26:12 AM 27 - 1958 0.00 0.00 0.00 0.00 7 |__mysqld
09:26:12 AM 27 - 1959 0.00 0.00 0.00 0.00 7 |__mysqld
09:26:12 AM 27 - 1960 0.00 0.00 0.00 0.00 7 |__mysqld
09:26:12 AM 27 - 1965 0.00 0.00 0.00 0.00 2 |__mysqld
09:26:12 AM 27 - 1966 0.00 0.00 0.00 0.00 7 |__mysqld
09:26:12 AM 27 - 1967 0.00 0.00 0.00 0.00 3 |__mysqld
09:26:12 AM 27 - 1968 0.00 0.00 0.00 0.00 1 |__mysqld
09:26:12 AM 27 - 1969 0.00 0.00 0.00 0.00 1 |__mysqld
09:26:12 AM 27 - 1970 0.00 0.00 0.00 0.00 5 |__mysqld
09:26:12 AM 27 - 1971 0.00 0.00 0.00 0.00 5 |__mysqld
09:26:12 AM 27 - 1972 0.00 0.00 0.00 0.00 1 |__mysqld
09:26:12 AM 27 - 1973 0.00 0.00 0.00 0.00 1 |__mysqld
09:26:12 AM 27 - 1974 0.00 0.00 0.00 0.00 5 |__mysqld
09:26:12 AM 27 - 1975 0.00 0.00 0.00 0.00 6 |__mysqld
09:26:12 AM 27 - 1976 0.00 0.00 0.00 0.00 5 |__mysqld
09:26:12 AM 27 - 1977 0.00 0.00 0.00 0.00 2 |__mysqld
09:26:12 AM 27 - 1978 0.00 0.00 0.00 0.00 5 |__mysqld
09:26:12 AM 27 - 1982 2.00 0.00 0.00 2.00 2 |__mysqld
09:26:12 AM 27 - 1983 21.00 1.00 0.00 22.00 4 |__mysqld
09:26:12 AM 27 - 1984 94.00 1.00 0.00 95.00 3 |__mysqld
09:26:12 AM 27 - 1987 18.00 0.00 0.00 18.00 5 |__mysqld
09:26:12 AM 27 - 1988 11.00 0.00 0.00 11.00 1 |__mysqld
09:26:12 AM 27 - 2136 0.00 0.00 0.00 0.00 6 |__mysqld
09:26:12 AM 27 - 50676 11.00 0.00 0.00 11.00 7 |__mysqld
09:26:12 AM 27 - 38906 9.00 0.00 0.00 9.00 5 |__mysqld
Los threads (hilos marcados presentan un consumo marcadamente superior al resto, por lo que su análisis revelará el origen de l problema

En mysql phpmyadmin

SELECT `THREAD_ID`, `PROCESSLIST_COMMAND`, `PROCESSLIST_STATE`, `PROCESSLIST_INFO` FROM `threads` WHERE `THREAD_OS_ID` = <thread>

Thread Command State Info

1982 Query Creating sort SELECT SQL_CALC_FOUND_ROWS l7ZzkK_posts.ID
Index FROM l7ZzkK_posts
WHERE 1=1 AND (((l7ZzkK_posts.post_title LIKE '%cande%') OR (l7ZzkK_posts.post_excerpt LIKE '%cande%')
OR (l7ZzkK_posts.post_content LIKE '%cande%'))) AND (l7ZzkK_posts.post_password = '') AND
l7ZzkK_posts.post_type IN ('post', 'page', 'attachment', 'product', 'vc4_templates') AND ((l7ZzkK_posts.post_status
= 'publish'))
ORDER BY l7ZzkK_posts.post_title LIKE '%cande%' DESC, l7ZzkK_posts.post_date DESC LIMIT 0, 4
1983 Query Sending data SELECT t.*, tt.* FROM l7ZzkK_terms AS t INNER JOIN l7ZzkK_term_taxonomy AS tt ON t.term_id = tt.term_id
WHERE t.term_id IN
(44,30356,28998,44520,23143, 34773,27977,23347,43412,35586, 29974,35139,22201,12740,44562, 250, 24785,170
08,1936,5419,32008, 6020,29427,32355, 13892,27218,33634,38187,47980, 28251,17703,4834, 16795,37195,3041,1
5787,21333,16851,6554,19947, 22983,9997,15203, 22125,22120,1344, 15832,5158,21462, 24676,13908,25748,142
45,24335,21396,21108,329,17770,5671, 38033,36509,39860,381,37875,5295,38036,38417,39531,43604,36961,36
564,13909,36905,47920,48380, 23804,34558,48391,32360,35163, 32059,18978,46158,31156,36131, 38308,44893,
44461,43898,38463,33749, 38316,34872,35233,45405,43858,34943,31627,45641,45446,34809,33507,36947,4635
6,34662,43302,34925,33217,35594, 36680,39284,35614,33722,41963, 27836,37945,38337,41713,33218, 36940,34
800,36487,38912,35091,34926, 35014,35087,41331,33219,48315, 28375,32855,32468,39114,45149, 44996,36750,
36747,33920,31441,33475, 36928,34775,36833,35152,35823,32615,44802,33132,35078,38004,33673,39575,35
1984 Query Sending data SELECT post_id, meta_value FROM l7ZzkK_postmeta WHERE meta_key = '_wp_attached_f ile' AND meta_value =
'2022/02/logo-elsiglo-1-300x100-1.png
1985 Query Creating sort SELECT SQL_CALC_FOUND_ROWS l7ZzkK_posts.ID
Index FROM l7ZzkK_posts
WHERE 1=1 AND (((l7ZzkK_posts.post_title LIKE '%incendio%') OR
(l7ZzkK_posts.post_excerpt LIKE '%incendio%') OR (l7ZzkK_posts.post_content LIKE
'%incendio%'))) AND (l7ZzkK_posts.post_password = '') AND ((l7ZzkK_posts.post_type =
'post' AND (l7ZzkK_posts.post_status = 'publish')) OR (l7ZzkK_posts.post_type = 'page' YES
AND (l7ZzkK_posts.post_status = 'publish')) OR (l7ZzkK_posts.post_type = 'attachment'
AND (l7ZzkK_posts.post_status = 'publish')) OR (l7ZzkK_posts.post_type = 'product' AND
(l7ZzkK_posts.post_status = 'publish')))
ORDER BY l7ZzkK_posts.post_title LIKE '%incendio %' DESC, l7ZzkK_posts.post_date
DESC LIMIT 0, 10

1986 Query SELECT t.*, tt.* FROM l7ZzkK_terms AS t INNER JOIN l7ZzkK_term_taxonomy AS tt ON t.term_id = tt.term_id
WHERE t.term_id IN
(44,30356,28998,44520,23143, 34773,27977,23347,43412,35586, 29974,35139,22201,12740,44562, 250, 24785,170
08,1936,5419,32008, 6020,29427,32355, 13892,27218,33634,38187,47980, 28251,17703,4834, 16795,37195,3041,1
 5787,21333,16851,6554,19947, 22983,9997,15203, 22125,22120,1344, 15832,5158,21462, 24676,13908,25748,142
45,24335,21396,21108,329,17770,5671, 38033,36509,39860,381,37875,5295,38036,38417,39531,43604,36961,36
564,13909,36905,47920,48380, 23804,34558,48391,32360,35163, 32059,18978,46158,31156,36131, 38308,44893,
44461,43898,38463,33749, 38316,34872,35233,45405,43858,34943,31627,45641,45446,34809,33507,36947,4635
6,34662,43302,34925,33217,35594, 36680,39284,35614,33722,41963, 27836,37945,38337,41713,33218, 36940,34
800,36487,38912,35091,34926, 35014,35087,41331,33219,48315, 28375,32855,32468,39114,45149, 44996,36750,
36747,33920,31441,33475, 36928,34775,36833,35152,35823,32615,44802,33132,35078,38004,33673,39575,35
1987 Query Sending data SELECT `PROCESSLIST_COMMAND`, `PROCESSLIST_STATE`, `PROCESSLIST_INFO`,
`HISTORY` FROM `threads` WHERE `THREAD_OS_ID`=1987 LIMIT 0, 25

1988 Query Sending data SELECT option_name, option_value FROM l7ZzkK_options WHERE autoload = 'yes'

2136 Query Sending data SELECT option_name, option_value FROM l7ZzkK_options WHERE autoload = 'yes'

50676 Query Sending data SELECT option_name, option_value FROM l7ZzkK_options WHERE autoload = 'yes'

38906 Query Creating sort SELECT t.*, tt.* FROM l7ZzkK_terms AS t INNER JOIN l7ZzkK_term_taxonomy AS tt ON t.term_id = tt.term_id
index WHERE t.term_id IN
(44,30356,28998,44520,23143, 34773,27977,23347,43412,35586, 29974,35139,22201,12740,44562, 250, 24785,170
08,1936,5419,32008, 6020,29427,32355, 13892,27218,33634,38187,47980, 28251,17703,4834, 16795,37195,3041,1
5787,21333,16851,6554,19947, 22983,9997,15203, 22125,22120,1344, 15832,5158,21462, 24676,13908,25748,142
45,24335,21396,21108,329,17770,5671, 38033,36509,39860,381,37875,5295,38036,38417,39531,43604,36961,36
564,13909,36905,47920,48380, 23804,34558,48391,32360,35163, 32059,18978,46158,31156,36131, 38308,44893,
44461,43898,38463,33749, 38316,34872,35233,45405,43858,34943,31627,45641,45446,34809,33507,36947,4635
6,34662,43302,34925,33217,35594, 36680,39284,35614,33722,41963, 27836,37945,38337,41713,33218, 36940,34
800,36487,38912,35091,34926, 35014,35087,41331,33219,48315, 283 75,32855,32468,39114,45149, 44996,36750,
36747,33920,31441,33475, 36928,34775,36833,35152,35823,32615,44802,33132,35078,38004,33673,39575,35
Hay una actividad altamente repetitiva (el muestreo se hizo a frecuencia de 1seg)
que involucra creación de índices. Esto está ligado a actividades (plugins de estadística) SEO, ADS y
registro de eventos de usuarios.

Revisando el plugin Yoast SEO, éste no permite su optimización (consiste en creación de índices
para minimizar el impacto en la ejecución del servidor)
Revisión de logs Mysql, Apache

2022-08-12T03:35:09.353819Z 82 [Note] Sort aborted, host: localhost, user: esnewser_wp_zdmrf,

thread: 82, error: Server shutdown in progress, query: SELECT SQL_CALC_FOUND_ROWS
l7ZzkK_posts.ID
FROM l7ZzkK_posts
WHERE 1=1 AND (((l7ZzkK_posts.post_title LIKE '%su%')
OR (l7ZzkK_posts.post_excerpt LIKE '%su%') OR (l7ZzkK_posts.post_content LIKE '%su%'))) AND
(l7ZzkK_posts.post_password = '') AND l7ZzkK_posts.post_type IN ('post', 'page', 'attachment',
'product', 'vc4_templates') AND ((l7ZzkK_posts.post_status = 'publish'))

ORDER BY l7ZzkK_posts.post_title LIKE '%su%' DESC,

l7ZzkK_posts.post_date DESC
LIMIT 0, 4
2022-08-12T03:35:09.353860Z 83 [Note] Sort aborted, host: localhost, user: esnewser_wp_zdmrf,
thread: 83, error: Server shutdown in progress, query: SELECT SQL_CALC_FOUND_ROWS
l7ZzkK_posts.ID
FROM l7ZzkK_posts
WHERE 1=1 AND (((l7ZzkK_posts.post_title LIKE '%suc%')
OR (l7ZzkK_posts.post_excerpt LIKE '%suc%') OR (l7ZzkK_posts.post_content LIKE '%suc%'))) AND
(l7ZzkK_posts.post_password = '') AND l7ZzkK_posts.post_type IN ('post', 'page', 'attachment',
'product', 'vc4_templates') AND ((l7ZzkK_posts.post_status = 'publish'))

ORDER BY l7ZzkK_posts.post_title LIKE '%suc%' DESC,

l7ZzkK_posts.post_date DESC
LIMIT 0, 4

2022-08-12T03:44:37.314701Z 276 [Note] Sort aborted, host: localhost, user:

esnewser_wp_zdmrf, thread: 276, error: Server shutdown in progress, query: SELECT t.term_id
FROM l7ZzkK_terms AS t INNER JOIN l7ZzkK_term_taxonomy AS tt ON
t.term_id = tt.term_id

ORDER BY t.name ASC

Los errores pueden ocurrir porque se excede el tiempo máximo para ejecución de transacciones
debido a la ausencia de índices (deben crearse en cada solicitud)

Solución propuesta

Habilitación de cache de transacciones del servidor Mysql (128M)

Esperar la próxima actualización de Yoast SEO para activar su optimización
Efecto

El efecto logrado consiste en una menor saturación del conjunto de procesadores por el uso del
caché, que puede mejorar en la medida que se optimicen los procesos de los plugins de SEO y de
registro de actividades sobre publicaciones (ADS).

Se hará seguimiento del comportamiento del servidor, si antes de estar disponible la actualización
de plugin SEO se vuelve a presentar un compromiso del desempeño o ejecución adecuada del sitio
web, se pueden implementar otros niveles de caché en el servidor, pero cuya configuración
ameritaría detener el servicio al menos un día.