percona 5.7.18-16 crash
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
New
|
Undecided
|
Unassigned | |||
5.6 |
New
|
Undecided
|
Unassigned | |||
5.7 |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
We use Percona on more than 300 servers. We have the latest version of 5.7.18-16
I read about this probles - https:/
If I understand correctly in new versions of the Percona Server this is not corrected?
Crach report.
09:20:30 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=509
thread_count=20
connection_count=20
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f5a95b456b0 db: vkonta8w_direct
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f6279ebce40 thread_stack 0x80000
/usr/bin/
/usr/bin/
/lib/x86_
/lib/x86_
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f5adb328890): UPDATE `direct_
Connection ID (thread ID): 36365381
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
atom2 : ~ [0] # free -m
total used free shared buff/cache available
Mem: 257738 60042 17785 28328 179910 155472
Swap: 0 0 0
atom2 : ~ [0] # cat /etc/docker/
#######
# Main config
#######
[mysqld]
#######
# Common
#######
# wait timeout (drop long sleeping clients)
interactive_timeout = 30
wait_timeout = 30
# system setting
user = mysql
pid-file = /var/run/
socket = /var/run/
basedir = /usr
datadir = /home/mysql
tmpdir = /home/tmpfs
# bind settings
# see conf.d
# external locking for myisam tables
skip_external_
delay_key_write = ON
# default character set
character-
collation-server = utf8_general_ci
# threads settings
thread_stack = 2048K
thread_cache_size = 96
# extra connections
extra_port = 3308
extra_max_
# connections
max_user_
max_connections = 409
back_log = 65535
# beget cgroups
# per-connections buffers
# (join_buffer_size + read_buffer_size + sort_buffer_size + read_rnd_
join_buffer_size = 3299046
read_buffer_size = 3299046
read_rnd_
sort_buffer_size = 3299046
# disable query cache
# (due to global mutex we may have degraded performance in high concurrence environment)
query_cache_type = 1
query_cache_size = 0
query_cache_limit = 1048576
query_cache_
query_cache_
# max blob size
max_allowed_packet = 33554432
group_concat_
# sql mode (bitrix requirement)
sql_mode =
# tmp tables
tmp_table_size = 5405157621
max_heap_table_size = 5405157621
# max errors before kick client out
max_connect_errors = 65000
max_error_count = 65000
# open files limit (maximum possible)
open_files_limit = 1048576
# open table cache
table_open_cache = 50000
table_definitio
table_open_
# disable auto flush by default (do it manually by cron)
flush_time = 0
# general log settings
log_error = /var/log/
log_warnings = 2
# slow log settings
slow_query_log = ON
slow_query_log_file = /var/log/
long_query_time = 2
# low priority updates
low_priority_
# metadata locks
metadata_
# insert buffer
bulk_insert_
# delayed insert
delayed_
max_delayed_threads = 0
#max search depth for query optimizer
optimizer_
# performance schema
performance_schema = OFF
# enable percona userstat feature
userstat = ON
# preload buffer
preload_buffer_size = 65535
# query alloc size
query_alloc_
query_prealloc_size = 16384
# transactions alloc size
transaction_
transaction_
# transaction isolation level
transaction-
# case sensitivity
lower_case_
#######
# MyISAM
#######
# recover type
myisam_
# recovery buffer
myisam_
# key buffer
key_buffer_size = 10810315243
#fulltext
ft_min_word_len = 4
#######
# InnoDB
#######
# separate tablespace
innodb_
# file format
innodb_file_format = 'Barracuda'
# log files
innodb_
innodb_
# open files
innodb_open_files = 50000
# innodb threads
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_
# I/O optimization
innodb_
innodb_
innodb_
innodb_flush_method = O_DIRECT
# buffer pools
innodb_
innodb_
innodb_
innodb_
# preload buffer pool
innodb_
innodb_
# percona specific feature
innodb_
innodb_
# innodb fulltext
innodb_
innodb_
innodb_
# innodb large prefix
innodb_large_prefix = 1
# interval between successive column values
auto-increment-
auto-increment-
# innodb strict mode
innodb_strict_mode = 0
# innodb old block sublist
innodb_
# innodb temp data file
innodb_
# innodb numa policy
innodb_
#######
# client settings
#######
[mysqldump]
quick
quote-names
max_allowed_packet = 32M
[mysql]
[isamchk]
key_buffer = 32M
[client]
port = 3306
socket = /var/run/
[mysqld_safe]
socket = /var/run/
nice = 0
#######
# includes
#######
!includedir /etc/mysql/conf.d/
# EOF
summary: |
- percona 5.7.18-16 crach + percona 5.7.18-16 crash |
Hi Alexey,
Yes, latest Percona Server should be affected by this bug.
The bug you are referring require check with mysql 5.7.19, you can try to verify it with upstream mysqld or provide reproducible test case / test conditions.