MariaDB 10.2.14 (Tem timeout lendo os pacotes de comunicação)

1

Eu sou visto mensagens de aviso nos meus registros do servidor MariaDB. Estes estão lá, eu tentei muitas coisas.

Eu otimizei e consertei todos os meus bancos de dados, mas os avisos ainda estão lá.

2018-04-19 22:50:14 139673358411520 [Warning] Aborted connection 473891 to db: 'admin_******' user: 'admin_******' host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:52:43 139672739514112 [Warning] Aborted connection 474608 to db: 'admin_****** user: 'admin_****** host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:53:31 139672741635840 [Warning] Aborted connection 474834 to db: 'admin_******' user: 'admin_******' host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:54:16 139672739514112 [Warning] Aborted connection 475117 to db: 'admin_******' user: 'admin_******' host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:55:49 139672740726528 [Warning] Aborted connection 475696 to db: 'admin_******' user: 'admin_******' host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:55:53 139672740120320 [Warning] Aborted connection 475717 to db: 'admin_******ine' user: 'admin_******ine' host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:56:43 139673235744512 [Warning] Aborted connection 476011 to db: 'admin_******lin' user: 'admin_******lin' host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:56:57 139673235138304 [Warning] Aborted connection 476095 to db: 'admin_******ine' user: 'admin_******ine' host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:57:20 139672742545152 [Warning] Aborted connection 476186 to db: 'admin_****** user: 'admin_****** host: 'localhost' (Got timeout reading communication packets)

2018-04-19 22:57:51 139673235441408 [Warning] Aborted connection 476340 to db: 'admin_******ine' user: 'admin_******ine' host: 'localhost' (Got timeout reading communication packets)

Meu my.cnf

skip-external-locking
key_buffer_size = 256M
max_allowed_packet = 500M
table_open_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
thread_concurrency = 8

innodb_file_per_table

max_connections=500
wait_timeout=60
interactive_timeout=60
long_query_time=5

Estou usando o CentOS 7 com 8 GB de RAM.

Alguém pode me ajudar?

    
por Hassaan 19.04.2018 / 20:45

2 respostas

0

Resolva esse problema lendo as incompatibilidades link página da web. O problema já existia em versões anteriores porque log_warnings usam como padrão 1 e agora são padronizados como 2.

Defina dinamicamente o log_warnings = 1 global; e observe as mensagens pararem quase que imediatamente, redefina para 2 e dentro de 3 a 5 minutos as mensagens são retomadas.

Isso explica por que 10.2.14 eles simplesmente aparecem, mas os problemas reais provavelmente estão relacionados ao tratamento incorreto de exceções de aplicativos.

    
por 10.05.2018 / 20:36
0

Sugestões a considerar para sua seção my.cnf-ini [mysqld]

Lidere com # ou REMOVE para permitir que os padrões funcionem para você. . sort_buffer_size . read_buffer_size . read_rnd_buffer_size . thread_concurrency

altere esta variável global

thread_cache_size=100  # from 8 to reduce threads_created count
    
por 15.06.2018 / 23:01