Showing 1-30 of 53 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
113489 | 2023-12-22 7:43 | 2024-01-04 3:36 | MySQL Server: Replication | Can't repeat (335 days) | S3 | 5.7.26 5.7.36 5.7.44 | Any | Any | gtid_executed table lost the last binlog gtids |
113539 | 2024-01-02 19:44 | 2024-02-13 1:00 | MySQL Server: Replication | No Feedback (296 days) | S3 | 5.7 | Any | Any | Binlog replication in single threaded doesn't update transactional info table |
113564 | 2024-01-05 10:49 | 2024-11-07 14:39 | MySQL Server: Replication | Verified (176 days) | S5 | 8.0 | Any (>= glibc 2.25 ) | Any | write-only mode performance decreases by 15% in heavy workload |
113634 | 2024-01-12 17:33 | 2024-01-14 9:16 | MySQL Server: Replication | Verified (325 days) | S3 | 8.0 | Any | Any | Contribution: fix plugin semisync find minAck bug |
113663 | 2024-01-17 11:37 | 2024-01-17 12:04 | MySQL Server: Replication | Can't repeat (322 days) | S3 | 8.0.32 | CentOS | x86 | Crash occurs when applying binlog_transaction_dependency_tracking to slave node. |
113707 | 2024-01-22 11:52 | 2024-01-22 12:04 | MySQL Server: Replication | Verified (317 days) | S3 | 8.3.0, 8.0.36 | Any | Any | replication stops after updating geometry column |
113727 | 2024-01-23 14:34 | 2024-01-26 6:39 | MySQL Server: Replication | Verified (313 days) | S1 | 8.0.19+ | Any | Any | GTID Replica stalls completely when log_slave_updates=0 and a local DDL executed |
113769 | 2024-01-26 2:42 | 2024-03-01 1:00 | MySQL Server: Replication | No Feedback (279 days) | S3 | 5.7.44 | Any | Any | Generated column json binary format is incorrent |
113813 | 2024-01-31 2:26 | 2024-02-07 8:24 | MySQL Server: Replication | Verified (308 days) | S3 | MySQL8.0,8.0.36 | Any | Any | Semisync will abort due to wrong transaction binlog postion comparison |
113814 | 2024-01-31 2:42 | 2024-01-31 13:16 | MySQL Server: Replication | Verified (308 days) | S3 | MySQL8.0,5.7 | Any | Any | The Rpl_semi_sync_master_yes_tx and Rpl_semi_sync_master_no_tx are inaccurate |
114074 | 2024-02-21 8:35 | 2024-02-27 14:20 | MySQL Server: Replication | Verified (287 days) | S5 | 8.0.32 | Any | Any | optimize for Writeset_trx_dependency_tracker::get_dependency |
114117 | 2024-02-26 10:13 | 2024-03-21 6:20 | MySQL Server: Replication | Unsupported (258 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 |
114125 | 2024-02-26 15:51 | 2024-02-27 13:37 | MySQL Server: Replication | Verified (282 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 |
114198 | 2024-03-04 4:21 | 2024-03-07 7:23 | MySQL Server: Replication | Verified (273 days) | S3 | 8.0.35, 8.0.36 | Any | Any | Using PERSIST on binlog_transaction_compression partially compresses binary log |
114273 | 2024-03-08 2:04 | 2024-04-09 1:00 | MySQL Server: Replication | No Feedback (240 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 |
114310 | 2024-03-12 4:14 | 2024-03-19 7:24 | MySQL Server: Replication | Verified (267 days) | S3 | 8.0.33 | Any | Any | Master_compression_algorithm output is wrong |
114361 | 2024-03-15 1:53 | 2024-08-14 9:34 | MySQL Server: Replication | Verified (261 days) | S5 | 8.0 | Any | Any | Unaligned Delegate's lock reduces performance |
114472 | 2024-03-25 7:17 | 2024-03-25 7:20 | MySQL Server: Replication | Verified (254 days) | S3 | V8.0 | Any | Any | MySQL replica encounter error when master and replica innodb_strict_mode=OFF |
114511 | 2024-03-29 7:05 | 2024-04-02 9:58 | MySQL Server: Replication | Not a Bug (246 days) | S3 | MySQL8.0.22 | Any | Any | Turn on binlog compression and read binlog generate by big transaction cause oom |
114588 | 2024-04-09 1:34 | 2024-04-09 14:49 | MySQL Server: Replication | Verified (239 days) | S3 | 8.0 | Any | Any | Setting the instance to super-read-only still allows the flush priveleges comman |
114694 | 2024-04-19 2:24 | 2024-05-07 8:08 | MySQL Server: Replication | Verified (211 days) | S3 | 8.0.34 | Any (CentOS Linux release 7.6.1810 (Core) ) | Any | binlog_transaction_compression not effect on slave |
114699 | 2024-04-19 5:16 | 2024-04-22 9:35 | MySQL Server: Replication | Verified (226 days) | S1 | 8.0.36 | Any | Any | Inconsistent XA between master and slave if crash |
114776 | 2024-04-25 7:00 | 2024-04-25 7:51 | MySQL Server: Replication | Duplicate (223 days) | S3 | 8.0.32 | Any | Any | mysqlbinlog cannot print geometry correct |
114934 | 2024-05-09 7:33 | 2024-06-05 2:06 | MySQL Server: Replication | Can't repeat (182 days) | S3 | 5.7.44 | Any | Any | In Heavy workload, it degenerates to use single thread replication in fact |
115024 | 2024-05-16 5:04 | 2024-05-17 20:46 | MySQL Server: Replication | Can't repeat (201 days) | S2 | 8.0.33 | Linux (Rocky Linux release 8.9) | Any | MySQL Crash occurs during MySQL Replication stop process |
115189 | 2024-05-31 19:54 | 2024-06-10 23:10 | MySQL Server: Replication | Verified (182 days) | S3 | 8.4.0, 8.0.37 | Any | Any | P_S Digest table unexpectedly reports created database on replica |
115203 | 2024-06-03 17:34 | 2024-06-10 23:09 | MySQL Server: Replication | Verified (184 days) | S3 | 8.4.0, 8.0.37 | Any | Any | Empty "use ;" on replica in slow query log file. |
115310 | 2024-06-12 20:33 | 2024-06-17 8:00 | MySQL Server: Replication | Verified (170 days) | S2 | 8.4.0 | Any | Any | Granting SET_USER_ID breaks replication from 8.0 to 8.4. |
115344 | 2024-06-14 23:49 | 2024-06-17 8:02 | MySQL Server: Replication | Verified (170 days) | S3 | 8.4.0 | Any | Any | Terminology update for mysql internal tables |
115355 | 2024-06-17 8:58 | 2024-06-17 14:55 | MySQL Server: Replication | Verified (170 days) | S3 | 8.4, 8.0.37 | Any | Any | SQLs in procedure make replication throw error |
Showing 1-30 of 53 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |