| Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 106875 | 2022-03-30 14:43 | 2022-04-05 14:13 | MySQL Server: Replication | Verified (354 days) | S3 | 8.0.28 | Any | Any | Contribution by Tencent: writeset can not be used when binlog_format is mixed |
| 106845 | 2022-03-26 13:23 | 2022-04-06 1:46 | MySQL Server: Replication | Verified (353 days) | S2 | 8.0.25 | CentOS (7.6) | ARM | Parallel replication not working with slave_preserve_commit_order=1 |
| 106999 | 2022-04-13 8:44 | 2022-04-14 12:02 | MySQL Server: Replication | Can't repeat (345 days) | S2 | 5.7.37 | Any | Any | contributed by Tencent: shutdown hang due to binlog dump stick at wait_new_event |
| 106942 | 2022-04-07 10:44 | 2022-04-19 9:40 | MySQL Server: Replication | Not a Bug (340 days) | S3 | 8.0.28 | Any | Any | alter user may lead replication broken with error 1396 |
| 106970 | 2022-04-08 16:55 | 2022-04-21 0:16 | MySQL Server: Replication | Verified (344 days) | S3 | 8.0.21 | Linux | x86 | Replicate_Wild_Do_Table don't take effect |
| 107113 | 2022-04-24 10:53 | 2022-04-26 4:17 | MySQL Server: Replication | Verified (335 days) | S3 | 5.7,8.0, 8.0.28 | Any | Any | Got fatal error 1236 from master when reading data from binary log |
| 107008 | 2022-04-13 11:44 | 2022-05-05 7:11 | MySQL Server: Replication | Verified (324 days) | S2 | 5.7.37 | Any | Any | Contribution by Tencent:Shutdown hang due to work thread wait for ack |
| 107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (308 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 107371 | 2022-05-23 11:12 | 2022-05-23 12:29 | MySQL Server: Replication | Verified (306 days) | S3 | Ver 8.0, 5.7 | Any | Any | slave error: Slave I/O for channel '': Unexpected master's heartbeat data |
| 107438 | 2022-05-31 19:57 | 2022-06-07 9:38 | MySQL Server: Replication | Verified (297 days) | S2 | 5.7.38 | CentOS (8) | Any | JSON STORED generated column values are inserted as NULL on replica |
| 107677 | 2022-06-28 7:41 | 2022-06-28 8:18 | MySQL Server: Replication | Verified (270 days) | S2 | 8.0.29, 5.7.38 | Any | Any | Contribution by Tencent: create table like temporary table missing charset info |
| 107928 | 2022-07-20 23:09 | 2022-07-26 2:17 | MySQL Server: Replication | Verified (247 days) | S2 | 8.0 | Any | Any | MySQL 8.0 Replication breaks when tmpdir space is filled |
| 108061 | 2022-08-03 11:33 | 2022-08-04 2:01 | MySQL Server: Replication | Verified (233 days) | S3 | 5.7.39 | Any | Any | Contribution by Tencent: Generated column calculate error without base column |
| 108104 | 2022-08-10 3:06 | 2022-08-10 12:39 | MySQL Server: Replication | Not a Bug (227 days) | S5 | MySQL5.7.26 | Any | Any | LOCK_status affect transaction performance when do a "show status" command |
| 107884 | 2022-07-14 17:16 | 2022-08-17 1:00 | MySQL Server: Replication | No Feedback (221 days) | S3 | 8.0.29 | Any | Any | Error message after stop semi sync replication |
| 108405 | 2022-09-06 16:22 | 2022-09-07 4:56 | MySQL Server: Replication | Verified (199 days) | S3 | 8.0 | Any | Any | Contribution: Implement logic to be able to get a consistent GTID |
| 108510 | 2022-09-16 0:31 | 2022-09-16 5:36 | MySQL Server: Replication | Verified (190 days) | S2 | 8.0.21 | Any | Any | Return value of rotate() not get checked |
| 108514 | 2022-09-16 1:10 | 2022-09-16 5:53 | MySQL Server: Replication | Verified (190 days) | S2 | 8.0.21 | Any | Any | Return value of Gtid_set::ensure_sidno(int) not get checked |
| 108537 | 2022-09-19 13:29 | 2022-09-20 15:46 | MySQL Server: Replication | Verified (187 days) | S2 | 5.7 | Any | Any | gtid_subset should reset null_value to false |
| 108234 | 2022-08-23 7:00 | 2022-10-03 12:29 | MySQL Server: Replication | Can't repeat (173 days) | S3 | mysql 8.0.28 | Any | Any | A Document incorrect regarding Replication with Differing Table Definitions |
| 108682 | 2022-10-04 19:32 | 2022-10-09 12:48 | MySQL Server: Replication | Verified (170 days) | S2 | 5.7.39 | Any | Any | Read-Committed Isolation, UPDATES wrapped in DROP TEMPORARY TABLE IF EXISTS |
| 108876 | 2022-10-25 23:00 | 2022-10-27 17:22 | MySQL Server: Replication | Can't repeat (149 days) | S2 | 8.0.28 | CentOS ( 7.9.2009) | x86 | CLONE operation results in mysqld server hang on startup |
| 108892 | 2022-10-27 1:47 | 2022-10-31 3:32 | MySQL Server: Replication | Can't repeat (145 days) | S3 | 8.0.26 | CentOS (CentOS Linux release 7.6.1810) | Any | MGR Sencondary node don`t appling relay logs |
| 108834 | 2022-10-20 11:05 | 2022-11-04 14:14 | MySQL Server: Replication | Not a Bug (141 days) | S3 | all version | Any | Any | MySQL Online DDL add AUTO_INCREMENT |
| 109023 | 2022-11-08 4:24 | 2022-11-08 7:51 | MySQL Server: Replication | Verified (137 days) | S3 | 5.7,8.0.31 | Any | Any | Leak REPL_SLAVE_ACL privilege error is ambiguous |
| 109016 | 2022-11-07 11:51 | 2022-11-08 15:57 | MySQL Server: Replication | Verified (137 days) | S3 | 5.7.38 | Any | Any | Slave crashed when master restart |
| 108760 | 2022-10-13 7:12 | 2022-11-14 1:00 | MySQL Server: Replication | No Feedback (132 days) | S3 | 8.0.16 | CentOS | Any | show slave status hang |
| 108948 | 2022-11-01 7:50 | 2022-11-21 11:16 | MySQL Server: Replication | Unsupported (124 days) | S3 | 5.6 | Windows | Any | Getting mislead error message after successful replication set |
| 109031 | 2022-11-09 2:47 | 2022-11-30 9:00 | MySQL Server: Replication | Verified (116 days) | S3 | 5.7.38 | Any | Any | 'start slave' reports error after stopping slave during IO thd reconnecting |
| 108422 | 2022-09-08 8:42 | 2022-12-03 10:50 | MySQL Server: Replication | Closed (112 days) | S3 | 8.0.30 | Any | Any | Old terminology "START SLAVE" is still in Error/Warning messages. |
| Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
