Question

我将MySQL Databse MyISAM迁移到InnoDB，但仍然面临过去24小时的问题。它是一个wordpress数据库。当它是MyISAM我面临一些桌面崩溃。然后我转储并创建一个新数据库并更改为innoDB引擎。

150323 17:56:46 InnoDB: Completed initialization of buffer pool
    150323 17:56:47 InnoDB: highest supported file format is Barracuda.
    150323 17:56:49  InnoDB: Waiting for the background threads to start
    150323 17:56:50 InnoDB: 5.5.41 started; log sequence number 739930449
    150323 17:56:50 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
    150323 17:56:50 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
    150323 17:56:50 [Note] Server socket created on IP: '127.0.0.1'.
    150323 17:56:50 [Note] Event Scheduler: Loaded 0 events
    150323 17:56:50 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.41-0+wheezy1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
    Killed
    150323 17:58:55 mysqld_safe Number of processes running now: 0
    150323 17:58:55 mysqld_safe mysqld restarted
    150323 17:58:55 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
    150323 17:58:55 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
    150323 17:58:55 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
    150323 17:58:56 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
    150323 17:58:56 [Note] Plugin 'FEDERATED' is disabled.
    150323 17:58:56 InnoDB: The InnoDB memory heap is disabled
    150323 17:58:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    150323 17:58:56 InnoDB: Compressed tables use zlib 1.2.7
    150323 17:58:56 InnoDB: Using Linux native AIO
    150323 17:58:56 InnoDB: Initializing buffer pool, size = 128.0M
    150323 17:58:56 InnoDB: Completed initialization of buffer pool
    150323 17:58:56 InnoDB: highest supported file format is Barracuda.
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    150323 17:58:56  InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    150323 17:58:57  InnoDB: Waiting for the background threads to start
    150323 17:58:58 InnoDB: 5.5.41 started; log sequence number 740208077
    150323 17:58:58 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
    150323 17:58:58 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
    150323 17:58:58 [Note] Server socket created on IP: '127.0.0.1'.
    150323 17:58:58 [Note] Event Scheduler: Loaded 0 events
    150323 17:58:58 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.41-0+wheezy1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)

Answer 1

闻起来像是在没有运行mysql_update的情况下更新了版本。

其中一些[警告]闻起来像一个旧的my.cnf需要一些小的编辑。

128M可以用于“微型”2GB的“RAM”。

MySQL无法维持，自动重启没有任何错误

1 个答案: