Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.31, 10.3.22, 10.4.12
-
None
-
debian 10
Description
Hello,
I think I've just encountered a bug with the latest version of mariadb-server-10.3.
After a power failure mariadb start a crash recovery but it seems to loop on the same LSN for ever.
To fix it I uninstall everythning and install v10.3.21.
The crash recovery just run fine.
Version: '10.3.22-MariaDB-0+deb10u1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian 10 |
2020-02-25 23:46:30 0 [Note] InnoDB: Buffer pool(s) load completed at 200225 23:46:30 |
2020-02-26 20:31:14 0 [Note] InnoDB: Using Linux native AIO |
2020-02-26 20:31:14 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins |
2020-02-26 20:31:14 0 [Note] InnoDB: Uses event mutexes |
2020-02-26 20:31:14 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 |
2020-02-26 20:31:14 0 [Note] InnoDB: Number of pools: 1 |
2020-02-26 20:31:14 0 [Note] InnoDB: Using SSE2 crc32 instructions |
2020-02-26 20:31:14 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 3, chunk size = 128M |
2020-02-26 20:31:15 0 [Note] InnoDB: Completed initialization of buffer pool |
2020-02-26 20:31:15 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). |
2020-02-26 20:31:15 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=3388965427 |
2020-02-26 20:31:30 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:31:45 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:32:00 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:32:15 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:32:30 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:32:45 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:33:00 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:33:15 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:33:30 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:33:45 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:34:00 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:34:15 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:34:30 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:34:45 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
2020-02-26 20:35:00 0 [Note] InnoDB: Read redo log up to LSN=3388965888 |
mariad configuration:
[mysqld]
|
 |
skip-name-resolve
|
 |
query_cache_type = 0 |
query_cache_size = 0 |
 |
innodb_io_capacity = 3000 |
innodb_buffer_pool_size = 3G
|
innodb_buffer_pool_instances = 3 |
innodb_flush_method = O_DIRECT
|
 |
# Logs
|
log-error = /var/log/mysql/error.log
|
slow_query_log = 1 |
slow_query_log_file = /var/log/mysql/mysql-slow.log
|
long_query_time = 5 |
Attachments
Issue Links
- is caused by
-
-
- Closed
-
- relates to
-
-
- Closed
-