Showing all 17 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
31317 | 2007-10-01 15:13 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | No Feedback (5994 days) | S3 | 6.0.4-alpha-debug | Any | Any | falcon crash recovery not perfect yet |
35772 | 2008-04-02 14:27 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5598 days) | S1 | teleco version mysql-5.1.23 ndb-6.3.8 | Linux (Linux 2.6.18-4-686 #1 SMP i686 GNU/Linux) | Any | MySql Cluster Crashes and fails to recover |
41531 | 2008-12-17 6:12 | 2011-02-16 23:43 | MySQL Server | No Feedback (5510 days) | S1 | 5.1.24 | Linux | Any | mysql does crash recovery though the error log shows as normal shutdown. |
42186 | 2009-01-18 10:16 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5409 days) | S2 | 5.0.51a | Linux (Kubuntu 8.04) | Any | Mysql don't start after power off (mysqld got signal 11) |
65443 | 2012-05-28 21:18 | 2012-09-18 10:07 | MySQL Server: InnoDB storage engine | Duplicate (4229 days) | S1 | 5.6 | Any | Any | Failure when applying insert buffer changes during crash recovery |
67246 | 2012-10-16 1:41 | 2013-02-07 10:07 | MySQL Server: Documentation | Closed (4087 days) | S2 | 5.6.7-rc | Linux (ubuntu 12.04 server) | Any | --relay-log-recovery required for crash-proof slave |
69122 | 2013-05-02 6:06 | 2014-02-02 17:47 | MySQL Server: InnoDB storage engine | Closed (3870 days) | S3 | 5.1,5.6 | Any | Any | InnoDB doesn't redo-log insert buffer merge operation if it is done in-place |
81957 | 2016-06-21 16:52 | 2016-06-28 11:21 | MySQL Server: InnoDB storage engine | Duplicate (2850 days) | S3 | 5.5.48 | Any | Any | Segmentation fault during crash recovery after server couldn't write binlogs |
82938 | 2016-09-10 8:23 | 2016-09-14 14:16 | MySQL Server: InnoDB storage engine | Not a Bug (2772 days) | S3 | 5.7 | Any | Any | Document are not correct in the case of innodb_support_xa=true. |
82798 | 2016-08-30 9:54 | 2016-08-30 12:04 | MySQL Server: InnoDB storage engine | Verified (2787 days) | S2 | 5.6, 5.6.32 | Any | Any | Small buffer pools might be too small for rseg init during crash recovery |
87282 | 2017-08-02 10:40 | 2017-10-23 22:54 | Tests: Server | Verified (2387 days) | S3 | 8.0.2 | Any | Any | WL#9499 can cause extra warnings on every crashing testcase |
92998 | 2018-10-29 19:42 | 2018-11-19 16:07 | MySQL Server: mysqldump Command-line Client | Unsupported (1995 days) | S3 | 8.0.13 | CentOS (v 7) | Any | After finishing the backup with mysqldump, mysql crashes and restarts |
95122 | 2019-04-25 7:03 | 2019-04-25 13:54 | MySQL Server: InnoDB storage engine | Verified (1819 days) | S3 | 5.6, 5.7 | Any | Any | No need to get log_sys->log_flush_order_mutex during InnoDB crash recovery |
77476 | 2015-06-25 0:28 | 2019-11-28 1:00 | MySQL Server: InnoDB storage engine | No Feedback (1603 days) | S2 | 5.6-5.7 | Any | Any | innodb_force_recovery = 6 cannot recover ANY DATA when change buffer not empty |
62740 | 2011-10-14 15:34 | 2022-08-17 12:11 | MySQL Server: InnoDB storage engine | Verified (3961 days) | S1 | 5.5.15 | MacOS (10.6.8) | Any | Crashes during startup in crash recovery InnoDB |
108952 | 2022-11-01 12:13 | 2022-11-04 16:34 | MySQL Server: InnoDB storage engine | Unsupported (530 days) | S2 | 8.0.28 | CentOS (7.2) | x86 | data inconsistent since replica crash recovery after undo tablespace truncation |
110668 | 2023-04-12 12:36 | 2023-04-13 11:47 | MySQL Server: InnoDB storage engine | Unsupported (370 days) | S5 | 5.7.26, 5.7.29, 8.0.32 | Any | Any | Innodb crash recovery too slow if have wide table redo during apply phase |
Showing all 17 (Edit, Save, CSV, Feed) |