@kickbokser

Почему падает mysql на мощном оборудовании?

Всем привет, почему-то начал падать mysql, помогает только перезапуск и то не на долго. В логах такое:

170603  6:26:01 [Note] Event Scheduler: Purging the queue. 0 events
170603  6:26:03 [Warning] /usr/sbin/mysqld: Forcing close of thread 2405  user: 'имя_бд'
170603  6:26:03 [Warning] /usr/sbin/mysqld: Forcing close of thread 2266  user: 'имя_бд'
170603  6:26:03 [Warning] /usr/sbin/mysqld: Forcing close of thread 2057  user: 'имя_бд'
170603  6:26:03 [Warning] /usr/sbin/mysqld: Forcing close of thread 1630  user: 'имя_бд'
170603  6:26:03 [Warning] /usr/sbin/mysqld: Forcing close of thread 1148  user: 'имя_бд'
170603  6:26:03 [Warning] /usr/sbin/mysqld: Forcing close of thread 580  user: 'имя_бд'

170603  6:26:03  InnoDB: Starting shutdown...
170603  6:26:04  InnoDB: Shutdown completed; log sequence number 12030219985
170603  6:26:04 [Note] /usr/sbin/mysqld: Shutdown complete


Всего 140 бд на сервере, активно используется только процентов 20

Сервак хеон 16 cpu, 24 ram, ssd (в htop нагрузка нормальная, процессор ~50% и оперативки всего 10гб используется) Я пробовал менять параметры в my.cnf - ничего не помогает.

Содержимое my.cnf на данный момент
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# 
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port		= 3306
socket		= /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
log-error=/var/log/mysql.log
socket		= /var/run/mysqld/mysqld.sock
nice		= 0

[mysqld]
local-infile=0
innodb_file_per_table = 1
#
# * Basic Settings
#
user		= mysql
pid-file	= /var/run/mysqld/mysqld.pid
socket		= /var/run/mysqld/mysqld.sock
port		= 3306
basedir		= /usr
datadir		= /var/lib/mysql
tmpdir		= /tmp
lc-messages-dir	= /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
# bind-address		= 127.0.0.1
#
# * Fine Tuning
#
key_buffer		= 320M
max_allowed_packet	= 128M
thread_stack		= 1920K
thread_cache_size       = 80
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
max_connections        = 10000
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit	= 80M
query_cache_size        = 128M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
#log_slow_queries	= /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id		= 1
#log_bin			= /var/log/mysql/mysql-bin.log
expire_logs_days	= 10
max_binlog_size         = 1000M
bind-address= ::
#binlog_do_db		= include_database_name
#binlog_ignore_db	= include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet	= 128M

[mysql]
#no-auto-rehash	# faster start of mysql but no tab completition

[isamchk]
key_buffer		= 128M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/

[mysqld]
open_files_limit = 10000
wait_timeout = 57600
interactive_timeout = 57600
connect_timeout=5000
net_read_timeout=5000


За любую помощь буду очень благодарен
  • Вопрос задан
  • 1705 просмотров
Пригласить эксперта
Ответы на вопрос 2
Sheffild
@Sheffild
Сисадмин
У меня такое примерно было, когда линейка памяти ЕСС глюкнула, тогда она вроде работает, но результат возвращала не правильный и всё падало постоянно. Хотя есс считается мега памятью, но вот и на старуху нашлась пор..ха, я тогда почти неделю убил, даже всё перенёс на другой сервер, пока причину искал. Удивило то, что на другом аппарате всё работало хорошо. Может поможет
Ответ написан
@kickbokser Автор вопроса
Мне кажется я понял в чем дело. free -m показывает:

total used free shared buffers cached
Mem: 24100 23773 327 263 944 12548

У меня 24 гб оперативки. Я почему-то когда смотрю в htop там больше 11 гб не бывает...

0ec3f48cf71c4b84ba38a3efa2973f67.png
Ответ написан
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Похожие вопросы