Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
113663 | 2024-01-17 11:37 | 2024-01-17 12:04 | MySQL Server: Replication | Can't repeat (93 days) | S3 | 8.0.32 | CentOS | x86 | Crash occurs when applying binlog_transaction_dependency_tracking to slave node. |
113489 | 2023-12-22 7:43 | 2024-01-04 3:36 | MySQL Server: Replication | Can't repeat (106 days) | S3 | 5.7.26 5.7.36 5.7.44 | Any | Any | gtid_executed table lost the last binlog gtids |
113115 | 2023-11-17 2:20 | 2023-12-27 8:04 | MySQL Server: Replication | Can't repeat (114 days) | S3 | 5.7.21 | SUSE | Any | semi-sync slave exit checksum error and master exit with net_flush error |
113229 | 2023-11-27 7:57 | 2023-11-27 11:11 | MySQL Server: Replication | Can't repeat (144 days) | S3 | 8.0.33 | Any (CentOS Linux 7) | Any | mysqld: Duplicate entry 'mysql/slave_worker_info' for key 'tablespaces.name' |
111027 | 2023-05-15 10:49 | 2023-10-27 17:07 | MySQL Server: Replication | Closed (193 days) | S2 | 5.7.42, 8.0.33 | Any | Any | Multi-column indexes with writest will cause HA_ERR_FOUND_DUPP_KEY |
112030 | 2023-08-10 9:44 | 2023-08-18 14:38 | MySQL Server: Replication | Closed (245 days) | S2 | 8.0.22 | Linux (CentOS Linux 7 (Core)) | Other (3.10.0-1160.62.1.el7.x86_64 #1 SMP Tue Apr 5 16:57:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux) | MySQL 8.0.22 Bug Report: Inconsistent Replication to Multi-Channel Slave (No Err |
111149 | 2023-05-25 9:50 | 2023-11-03 20:32 | MySQL Server: Replication | Closed (255 days) | S3 | 8.0 | Any | Any | Lock leak in heartbeat_queue_event() |
113116 | 2023-11-17 2:29 | 2023-11-17 23:23 | MySQL Server: Replication | Duplicate (154 days) | S3 | 5.7.21 | SUSE | Any | master binlog_dump exit and then semi-sync slave report checksum error |
112979 | 2023-11-06 22:10 | 2023-11-08 0:33 | MySQL Server: Replication | Duplicate (164 days) | S3 | 8.0.35 | Any | Any | binlog_transaction_compression_level_zstd bug not fixed in 8.0.35 |
114273 | 2024-03-08 2:04 | 2024-04-09 1:00 | MySQL Server: Replication | No Feedback (11 days) | S3 | MySQL8.0.22 to 8.0.33 | Any | Any | turn on the binlog compression and load large data to server will cause oom |
113769 | 2024-01-26 2:42 | 2024-03-01 1:00 | MySQL Server: Replication | No Feedback (50 days) | S3 | 5.7.44 | Any | Any | Generated column json binary format is incorrent |
113539 | 2024-01-02 19:44 | 2024-02-13 1:00 | MySQL Server: Replication | No Feedback (67 days) | S3 | 5.7 | Any | Any | Binlog replication in single threaded doesn't update transactional info table |
112673 | 2023-10-10 6:43 | 2023-11-11 1:00 | MySQL Server: Replication | No Feedback (161 days) | S3 | 8.0.32 | CentOS | x86 | dump from slave with --dump-slave or --dump-replica option will change binlog |
114511 | 2024-03-29 7:05 | 2024-04-02 9:58 | MySQL Server: Replication | Not a Bug (17 days) | S3 | MySQL8.0.22 | Any | Any | Turn on binlog compression and read binlog generate by big transaction cause oom |
113219 | 2023-11-25 13:05 | 2023-12-06 8:02 | MySQL Server: Replication | Not a Bug (135 days) | S3 | MySQL8.0.34,MySQL8.2.0 | Linux | Any | Wrong value of auto_increment while executing load data replace |
112727 | 2023-10-15 4:17 | 2023-10-19 14:46 | MySQL Server: Replication | Not a Bug (183 days) | S3 | MySQL8.0.22, 8.0.23 | Any | Any | MySQL may couldn't solve the error when flush thread caches to binary logs |
111074 | 2023-05-18 12:15 | 2023-05-22 14:07 | MySQL Server: Replication | Not a Bug (333 days) | S2 | 8.0.33 | Red Hat (redhat 8.7) | x86 | start replica encounter Slave_SQL_Running NO with MY-013117 (null) |
110774 | 2023-04-23 13:52 | 2023-04-25 2:49 | MySQL Server: Replication | Not a Bug (360 days) | S3 | 8.0.33 | Any | Any | 'show replica status' set the field_flag of 'Second_Behind_Source' NOTNULL |
114117 | 2024-02-26 10:13 | 2024-03-21 6:20 | MySQL Server: Replication | Unsupported (29 days) | S3 | 5.7.24 | CentOS (7.8) | x86 (Intel(R) Xeon(R),2 cpu,2.5GHZ,) | Slave Abnormally stoped out of io thread error:Unknown error noted |
111242 | 2023-06-01 12:31 | 2023-06-06 16:10 | MySQL Server: Replication | Unsupported (318 days) | S2 | 5.7.41 and 8.0.33 | Any | Any | Replica Issue - ('mysql.infoschema'@'localhost') does not exist |
114588 | 2024-04-09 1:34 | 2024-04-09 14:49 | MySQL Server: Replication | Verified (10 days) | S3 | 8.0 | Any | Any | Setting the instance to super-read-only still allows the flush priveleges comman |
114472 | 2024-03-25 7:17 | 2024-03-25 7:20 | MySQL Server: Replication | Verified (25 days) | S3 | V8.0 | Any | Any | MySQL replica encounter error when master and replica innodb_strict_mode=OFF |
114361 | 2024-03-15 1:53 | 2024-03-19 11:11 | MySQL Server: Replication | Verified (32 days) | S5 | 8.0 | Any | Any | Unaligned Delegate's lock reduces performance |
114310 | 2024-03-12 4:14 | 2024-03-19 7:24 | MySQL Server: Replication | Verified (38 days) | S3 | 8.0.33 | Any | Any | Master_compression_algorithm output is wrong |
114198 | 2024-03-04 4:21 | 2024-03-07 7:23 | MySQL Server: Replication | Verified (44 days) | S3 | 8.0.35, 8.0.36 | Any | Any | Using PERSIST on binlog_transaction_compression partially compresses binary log |
114125 | 2024-02-26 15:51 | 2024-02-27 13:37 | MySQL Server: Replication | Verified (53 days) | S3 | 8.0.35,8.0.36 | CentOS (7.9) | x86 | Parameter set by SET PERSIST is not set to replication threads when restart |
114074 | 2024-02-21 8:35 | 2024-02-27 14:20 | MySQL Server: Replication | Verified (58 days) | S5 | 8.0.32 | Any | Any | optimize for Writeset_trx_dependency_tracker::get_dependency |
113814 | 2024-01-31 2:42 | 2024-01-31 13:16 | MySQL Server: Replication | Verified (79 days) | S3 | MySQL8.0,5.7 | Any | Any | The Rpl_semi_sync_master_yes_tx and Rpl_semi_sync_master_no_tx are inaccurate |
113813 | 2024-01-31 2:26 | 2024-02-07 8:24 | MySQL Server: Replication | Verified (79 days) | S3 | MySQL8.0,8.0.36 | Any | Any | Semisync will abort due to wrong transaction binlog postion comparison |
113727 | 2024-01-23 14:34 | 2024-01-26 6:39 | MySQL Server: Replication | Verified (84 days) | S1 | 8.0.19+ | Any | Any | GTID Replica stalls completely when log_slave_updates=0 and a local DDL executed |
Showing 1-30 of 49 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |