| Bug #49122 | large numbers of tables(198*18 + 301) to cause table crash and so on | ||
|---|---|---|---|
| Submitted: | 26 Nov 2009 6:08 | Modified: | 24 Jan 2010 8:21 |
| Reporter: | peng jinyan | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Partitions | Severity: | S1 (Critical) |
| Version: | 5.1.33 | OS: | Any (Linux and windows) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | large tables | ||
[26 Nov 2009 6:08]
peng jinyan
[26 Nov 2009 6:22]
peng jinyan
and we have large numbers of error info in mysql error log: 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091119.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091120.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091121.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091122.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091123.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091124.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091125.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091126.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091127.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091128.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091129.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091130.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091201.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091202.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091203.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091204.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\nbc_webpost_20091205.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\system_log.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\web_log_20091117.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\web_log_20091118.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\web_log_20091119.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\web_log_20091120.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\web_log_20091121.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\web_log_20091122.frm' 091126 13:22:08 [ERROR] D:\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db\web_log_20091123.frm' mysql status : mysql> status; -------------- mysql Ver 14.14 Distrib 5.1.33, for Win32 (ia32) Connection id: 3975 Current database: stone_db Current user: stoneviewuser@localhost SSL: Not in use Using delimiter: ; Server version: 5.1.33-community-log MySQL Community Server (GPL) Protocol version: 10 Connection: localhost via TCP/IP Server characterset: utf8 Db characterset: utf8 Client characterset: latin1 Conn. characterset: latin1 TCP port: 3306 Uptime: 1 day 2 hours 34 min 52 sec Threads: 7 Questions: 4497414 Slow queries: 0 Opens: 95664 Flush tables: 160 70 Open tables: 33 Queries per second avg: 46.998 -------------- when i use mysqlcheck to auto_repair mysql all talbes , the mysqld crashed : 091126 10:29:11 [ERROR] d:\Program Files\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db_20091129\nat_log_20091129060.frm' 091126 10:29:13 [ERROR] d:\Program Files\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db_20091129\nat_log_20091129073.frm' 091126 10:29:16 [ERROR] d:\Program Files\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db_20091129\nat_log_20091129090.frm' 091126 10:29:16 [ERROR] d:\Program Files\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db_20091129\nat_log_20091129091.frm' 091126 10:29:16 [ERROR] d:\Program Files\HSM Server\Service\mysql\bin\Mysqld.exe: Incorrect information in file: '.\stone_db_20091129\nat_log_20091129092.frm' 091126 10:29:26 - mysqld got exception 0xc0000005 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=2097152 max_used_connections=8 max_threads=151 threads_connected=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1012664 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x1ccfa410 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... 0043BBB0 Mysqld.exe!ha_partition::get_from_handler_file()[ha_partition.cc:2329] 00440E27 Mysqld.exe!ha_partition::initialize_partition()[ha_partition.cc:355] 00441BA7 Mysqld.exe!partition_create_handler()[ha_partition.cc:110] 004426A6 Mysqld.exe!get_new_handler()[handler.cc:246] 005C03B4 Mysqld.exe!open_binary_frm()[table.cc:1114] 005C233A Mysqld.exe!open_table_def()[table.cc:630] 00522FA8 Mysqld.exe!get_table_share()[sql_base.cc:377] 0052307B Mysqld.exe!get_table_share_with_create()[sql_base.cc:456] 005255C5 Mysqld.exe!open_unireg_entry()[sql_base.cc:3868] 00528C6D Mysqld.exe!open_table()[sql_base.cc:2934] 00529BF2 Mysqld.exe!open_tables()[sql_base.cc:4586] 0052A14A Mysqld.exe!open_and_lock_tables_derived()[sql_base.cc:4989] 005AC13D Mysqld.exe!mysql_admin_table()[sql_table.cc:4213] 005ADC5B Mysqld.exe!mysql_analyze_table()[sql_table.cc:5099] 005551C9 Mysqld.exe!mysql_execute_command()[sql_parse.cc:2932] 7C9300B8 ntdll.dll!RtlFreeHeap() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 1CA72EE8=ANALYZE TABLE `session_log_20091129060` thd->thread_id=3722 thd->killed=NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 091126 10:37:15 InnoDB: Started; log sequence number 0 46419 091126 10:37:16 [Note] Event Scheduler: Loaded 0 events 091126 10:37:16 [Note] d:\Program Files\HSM Server\Service\mysql\bin\Mysqld.exe: ready for connections. Version: '5.1.33-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
[26 Nov 2009 6:58]
Valeriy Kravchuk
Do you have the same problem on both Windows and Linux? Please, check with a newer version, 5.1.41, and, in case of the same problems, upload your my.cnf/my.ini file content.
[18 Dec 2009 3:20]
peng jinyan
thank you very much ! i am sorry to receive you email too latter! now we use it in windows,we will subordinate it to linux! the follow is my.ini. # Example MySQL config file for very large systems. # # This is for a large system with memory of 1G-2G where the system runs mainly # MySQL. # # You can copy this file to # /etc/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options (in this # installation this directory is C:\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 default-character-set=utf8 # [mysqld_multi] # mysqld = "C:/Program Files/MySQL/MySQL Server 5.1/mysqld" # mysqladmin = "C:/Program Files/MySQL/MySQL Server 5.1/mysqladmin" # user = root # password = 123456 # Here follows entries for some specific programs # The MySQL server [mysqld] port = 3306 basedir="D:/Program Files/HSM Server/Service/mysql/" datadir="D:/Program Files/HSM Server/Service/mysql/data_master/" default-character-set=utf8 skip-locking key_buffer = 384M max_allowed_packet = 2M table_cache = 512 sort_buffer_size = 2M read_buffer_size = 2M read_rnd_buffer_size = 8M myisam_sort_buffer_size = 64M thread_cache_size = 8 query_cache_size = 32M # Try number of CPU's*2 for thread_concurrency thread_concurrency = 8 #add open_files_limit = 2048 group_concat_max_len = 16384 slow_query_log = 1 # slave-skip-errors = ALL # keep log file 10 days # expire_logs_days = 2 # no need super privilege log-bin-trust-routine-creators=1 # 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! # #skip-networking # Disable Federated by default skip-federated # Replication Master Server (default) # binary logging is required for replication # 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 # # binary logging format - mixed recommended #binlog_format=mixed # Point the following paths to different dedicated disks #tmpdir = /tmp/ #log-update = /path-to-dedicated-directory/hostname # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = C:\mysql\data/ #innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend #innodb_log_group_home_dir = C:\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 = 384M #innodb_additional_mem_pool_size = 20M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 100M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50 [mysqldump] quick max_allowed_packet = 16M [mysql] default-character-set=utf8 no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout
[24 Dec 2009 8:21]
Sveta Smirnova
Thank you for the feedback. Please try current version 5.1.41 (or better upcoming 5.1.42 with fix for bug #46676): we have several bugs related to concurrent operations and FLUSH TABLES fixed lately. If problem still exists please provide output of SHOW CREATE TABLE for some of your partitioned tables.
[25 Jan 2010 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
