电源故障和mysql崩溃

电源故障和mysql崩溃,mysql,database,crash,innodb,Mysql,Database,Crash,Innodb,我在InnoDb引擎中使用MySql已经有一段时间了,我对它的性能非常满意。我有10张表,每秒更新两次。最近我停电了,如果不将innodb_force_恢复设置为至少4,就无法重新启动数据库。但是当试图修复损坏的表时,数据库将再次崩溃。我尝试过优化、检查、分析等等,但都导致了崩溃。 错误日志包含以下消息: InnoDB:错误:第570页日志序列号7289495 InnoDB:在未来!当前系统日志序列号5574939 最终,在删除了与特定表相关的所有文件后,我通过mysqldump(innodb_

我在InnoDb引擎中使用MySql已经有一段时间了,我对它的性能非常满意。我有10张表,每秒更新两次。最近我停电了,如果不将innodb_force_恢复设置为至少4,就无法重新启动数据库。但是当试图修复损坏的表时,数据库将再次崩溃。我尝试过优化、检查、分析等等,但都导致了崩溃。 错误日志包含以下消息:

InnoDB:错误:第570页日志序列号7289495 InnoDB:在未来!当前系统日志序列号5574939

最终,在删除了与特定表相关的所有文件后,我通过mysqldump(innodb_force_recovery为6)成功地转储了数据库。然后我重新安装了xampp并重新加载转储。这让我重新站起来跑步,只丢了一张桌子

我的问题是,一个损坏的表如何导致整个数据库崩溃

有没有一种方法可以最大限度地降低再次发生这种情况的风险,某种配置可以提高对电源故障的鲁棒性? 我知道显而易见的答案是将复制备份数据库保留在一个单独的服务器上,但由于处于开发的测试阶段,这似乎有些过头了

这是我正在使用的配置文件

# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# You can copy this file to
# C:/xampp2/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is C:/xampp2/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client] 
# password       = your_password 
port            = 3306 
socket          = "C:/xampp2/mysql/mysql.sock"


# Here follows entries for some specific programs 

# The MySQL server
[mysqld]
port= 3306
socket = "C:/xampp2/mysql/mysql.sock"
basedir = "C:/xampp2/mysql" 
tmpdir = "C:/xampp2/tmp" 
datadir = "C:/xampp2/mysql/data"
pid_file = "mysql.pid"
# enable-named-pipe
key_buffer = 16M
max_allowed_packet = 1G
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
log_error = "mysql_error.log"

# Change here for bind listening
# bind-address="127.0.0.1" 
# bind-address = ::1          # for ipv6

# Where do all the plugins live
plugin_dir = "C:/xampp2/mysql/lib/plugin/" 

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
# commented in by lampp security
#skip-networking
#skip-federated

# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id   = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin


# Point the following paths to different dedicated disks
#tmpdir = "C:/xampp2/tmp"
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir = "C:/xampp2/mysql/data"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "C:/xampp2/mysql/data"
#innodb_log_arch_dir = "C:/xampp2/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 2G
innodb_additional_mem_pool_size = 16M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 50M
innodb_log_buffer_size = 20M
innodb_flush_log_at_trx_commit = 2
innodb_lock_wait_timeout = 50
innodb_buffer_pool_instances = 4

## UTF 8 Settings
#init-connect=\'SET NAMES utf8\'
#collation_server=utf8_unicode_ci
#character_set_server=utf8
#skip-character-set-client-handshake
#character_sets-dir="C:/xampp2/mysql/share/charsets"

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
小型系统的MySQL配置文件示例。 #
#这适用于内存很少的系统(InnoDB在数据一致性方面非常保守。如果它捕获到任何意外情况(错误的校验和、头值等),它会故意崩溃,以避免损坏数据

如何“将这种情况再次发生的风险降至最低”


最好的方法是在trx\u提交时保持innodb\u flush\u log\u的安全默认值,
doublewrite
,等等。互联网上充斥着关于“如何让MySQL更快”的不经考虑的建议,但你知道,这是有价格的。innodb在数据一致性方面非常保守。如果它捕捉到任何意想不到的东西(错误的校验和、标题值或任何内容)它故意崩溃以不损坏数据

如何“将这种情况再次发生的风险降至最低”


最好的方法是在trx\u提交时保持innodb\u flush\u log\u的安全默认值,
doublewrite
,等等。互联网上充斥着关于“如何让MySQL更快”的轻率建议,但它是有价格的,你知道。

谢谢@HarshaW,这是一个很好的链接。我尝试了上面提到的所有内容,但始终无法恢复或修复损坏的表。正如我所说,备份数据库的唯一方法是重新安装mysql/xampp。谢谢@HarshaW,这是一个很好的链接。我尝试了上面提到的所有内容,但没有成功r能够恢复或修复损坏的表。正如我所说,备份数据库的唯一方法是重新安装mysql/xampp。我想知道你所说的安全默认值是什么意思?你知道设置这些参数的经验法则吗?innodb_flush_log_at_trx_commit当前设置为1,而doublewrite根本没有设置。对我来说,最重要的是精简g是健壮性和写效率。我不经常从数据库中读取数据。使用默认设置,Innodb是持久和最安全的。一些选项(包括上面提到的)以数据丢失或损坏风险为代价提高性能。我会首先排除危险的选项。为什么不发布my.cnf?我已更新了原始问题,将配置文件包括在内。提交时的
innodb\u flush\u log\u
为2,安全性较低。'innodb崩溃恢复工作与innodb\u flush\u log\u无关rx_提交设置。事务要么完全应用,要么完全擦除。“我想知道你说的安全默认值是什么意思?你知道设置这些参数的经验法则吗?提交时的innodb_flush_log_当前设置为1,而doublewrite根本没有设置。对我来说,最关键的是健壮性和写入效率。我不是经常从数据库中读取。使用默认设置,Innodb是持久和最安全的。一些选项(包括上述选项)以数据丢失或损坏风险为代价提高性能。我会首先排除危险的选项。为什么不发布my.cnf?我已更新了原始问题,将配置文件包括在内。提交时的
innodb\u flush\u log\u
为2,安全性较低。'innodb崩溃恢复工作与innodb\u flush\u log\u无关rx_提交设置。事务要么完全应用,要么完全擦除。”