Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.1.22
-
None
-
CloudLinux 6.8, CentOS 6.8, CloudLinux 7.3, CentoOS 7.3
Description
After the update from MariaDB 10.1.18 to 10.1.22 version I faced such trouble - starting of mysqld service is much longer than earlier(in 3 or 4 times). I use innodb_flush_method=O_DIRECT in /etc/my.cnf. When I switch innodb_flush_method to O_DSYNC, the start process restore to normal speed. If I downgrade to 10.1.18 version again, the start procedure becomes normal again even with O_DIRECT.
The log during restart:
2017-04-19 16:43:50 140691366845184 [Note] /usr/sbin/mysqld: Normal shutdown
|
|
|
2017-04-19 16:43:50 140691366845184 [Note] Event Scheduler: Purging the queue. 0 events
|
2017-04-19 16:43:51 140653317027584 [Note] InnoDB: FTS optimize thread exiting.
|
2017-04-19 16:43:51 140691366845184 [Note] InnoDB: Starting shutdown...
|
2017-04-19 16:43:52 140691366845184 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
|
2017-04-19 16:43:56 140691366845184 [Note] InnoDB: Shutdown completed; log sequence number 15475982614642
|
2017-04-19 16:43:56 140691366845184 [Note] /usr/sbin/mysqld: Shutdown complete
|
|
|
170419 16:43:56 mysqld_safe mysqld from pid file /var/lib/mysql/s11.zenbox.pl.pid ended
|
170419 16:43:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
|
/usr/sbin/mysqld: /usr/local/lib/libz.so.1: no version information available (required by /usr/sbin/mysqld)
|
2017-04-19 16:43:57 140603040954400 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
|
2017-04-19 16:43:57 140603040954400 [Note] /usr/sbin/mysqld (mysqld 10.1.22-MariaDB) starting as process 588916 ...
|
2017-04-19 16:43:57 7fe0b24f7820 InnoDB: Warning: Setting innodb_buffer_pool_populate is DEPRECATED and has no effect. This option will be removed in MariaDB 10.2.3.
|
2017-04-19 16:43:57 140603040954400 [Note] InnoDB: Using mutexes to ref count buffer pool pages
|
2017-04-19 16:43:57 140603040954400 [Note] InnoDB: The InnoDB memory heap is disabled
|
2017-04-19 16:43:57 140603040954400 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
2017-04-19 16:43:57 140603040954400 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
|
2017-04-19 16:43:57 140603040954400 [Note] InnoDB: Compressed tables use zlib 1.2.3
|
2017-04-19 16:43:57 140603040954400 [Note] InnoDB: Using Linux native AIO
|
2017-04-19 16:43:57 140603040954400 [Note] InnoDB: Using SSE crc32 instructions
|
2017-04-19 16:43:57 140603040954400 [Note] InnoDB: Initializing buffer pool, size = 30.0G
|
2017-04-19 16:43:58 140603040954400 [Note] InnoDB: Completed initialization of buffer pool
|
2017-04-19 16:43:59 140603040954400 [Note] InnoDB: Highest supported file format is Barracuda.
|
2017-04-19 16:45:13 140603040954400 [Note] InnoDB: 128 rollback segment(s) are active.
|
2017-04-19 16:45:13 140603040954400 [Note] InnoDB: Waiting for purge to start
|
2017-04-19 16:45:13 140603040954400 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 15475982614642
|
2017-04-19 16:45:13 140565010159360 [Note] InnoDB: Dumping buffer pool(s) not yet started
|
2017-04-19 16:45:13 140603040954400 [Note] Plugin 'FEEDBACK' is disabled.
|
2017-04-19 16:45:13 140603040954400 [Note] Server socket created on IP: '::'.
|
2017-04-19 16:45:13 140603040954400 [Warning] 'user' entry 'root@gdgggdgd' ignored in --skip-name-resolve mode.
|
2017-04-19 16:45:13 140603040954400 [Note] /usr/sbin/mysqld: ready for connections.
|
Version: '10.1.22-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
|
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
-
- Closed
-