[Gluster-users] mysql crashes after shutdown one glusterfs node

Darren Zhang hiscal at 126.com
Wed Feb 22 07:56:38 UTC 2017

I have two glusterfs servers and created a distrubuted volume:

Volume Name: mysql
Type: Distribute
Volume ID: 6e8accb1-1659-4e9a-b6ad-59e17c17b9cc
Status: Started
Snapshot Count: 0
Number of Bricks: 2
Transport-type: tcp
Options Reconfigured:
nfs.disable: on
performance.readdir-ahead: on
transport.address-family: inet
server.ssl: on
client.ssl: on
auth.ssl-allow: glusterfsclient

I mounted it to /var/lib/mysql and started a mysql container
Now, I need to maintain node and shut it down, since this is a distrubuted volume, so some files will be "disapear" for mysql for a while.
But mysql container failed to start then, even after back to work, mysql still failed to start.

2017-02-22T07:25:27.928023Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
 2017-02-22T07:25:27.930106Z 0 [Warning] Can't create test file /var/lib/mysql/c7cbff5f61a9.lower-test
 2017-02-22T07:25:27.930185Z 0 [Note] mysqld (mysqld 5.7.17) starting as process 1 ...
 2017-02-22T07:25:27.934393Z 0 [Warning] Can't create test file /var/lib/mysql/c7cbff5f61a9.lower-test
 2017-02-22T07:25:27.936965Z 0 [Warning] Can't create test file /var/lib/mysql/c7cbff5f61a9.lower-test
 2017-02-22T07:25:27.939402Z 0 [Note] InnoDB: PUNCH HOLE support available
 2017-02-22T07:25:27.939469Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 2017-02-22T07:25:27.939493Z 0 [Note] InnoDB: Uses event mutexes
 2017-02-22T07:25:27.939514Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
 2017-02-22T07:25:27.939552Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
 2017-02-22T07:25:27.939572Z 0 [Note] InnoDB: Using Linux native AIO
 2017-02-22T07:25:27.940383Z 0 [Note] InnoDB: Number of pools: 1
 2017-02-22T07:25:27.940789Z 0 [Note] InnoDB: Using CPU crc32 instructions
 2017-02-22T07:25:27.942845Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
 2017-02-22T07:25:27.951079Z 0 [Note] InnoDB: Completed initialization of buffer pool
 2017-02-22T07:25:27.953775Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
 2017-02-22T07:25:27.966441Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
es before creating new system tablespace.
 2017-02-22T07:25:27.968487Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
 2017-02-22T07:25:28.569053Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
 2017-02-22T07:25:28.569093Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
 2017-02-22T07:25:28.569102Z 0 [ERROR] Failed to initialize plugins.
 2017-02-22T07:25:28.569105Z 0 [ERROR] Aborting
 2017-02-22T07:25:28.569111Z 0 [Note] Binlog end
 2017-02-22T07:25:28.569186Z 0 [Note] Shutting down plugin 'MyISAM'
 2017-02-22T07:25:28.569211Z 0 [Note] Shutting down plugin 'CSV'
 2017-02-22T07:25:28.569654Z 0 [Note] mysqld: Shutdown complete

So my question is:
1) How to avoid downtime if volumes using distributed mode?
2) If question1 is impossible, how to avoid downtime when I need to maintain glusterfs servers?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170222/066fc608/attachment.html>

More information about the Gluster-users mailing list