Showing 1-30 of 43 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
115024 | 2024-05-16 5:04 | 2024-05-17 20:46 | MySQL Server: Replication | Can't repeat (346 days) | S2 | 8.0.33 | Linux (Rocky Linux release 8.9) | Any | MySQL Crash occurs during MySQL Replication stop process |
114934 | 2024-05-09 7:33 | 2024-06-05 2:06 | MySQL Server: Replication | Can't repeat (327 days) | S3 | 5.7.44 | Any | Any | In Heavy workload, it degenerates to use single thread replication in fact |
115203 | 2024-06-03 17:34 | 2024-06-10 23:09 | MySQL Server: Replication | Verified (329 days) | S3 | 8.4.0, 8.0.37 | Any | Any | Empty "use ;" on replica in slow query log file. |
115189 | 2024-05-31 19:54 | 2024-06-10 23:10 | MySQL Server: Replication | Verified (327 days) | S3 | 8.4.0, 8.0.37 | Any | Any | P_S Digest table unexpectedly reports created database on replica |
115310 | 2024-06-12 20:33 | 2024-06-17 8:00 | MySQL Server: Replication | Verified (315 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 (315 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 (315 days) | S3 | 8.4, 8.0.37 | Any | Any | SQLs in procedure make replication throw error |
115538 | 2024-07-08 8:58 | 2024-07-08 9:07 | MySQL Server: Replication | Verified (294 days) | S3 | 5.7 and 8.0 | Any | Any | mysqlbinlog missing some events when tmpdir not accessible |
115605 | 2024-07-16 11:27 | 2024-07-17 9:52 | MySQL Server: Replication | Verified (285 days) | S2 | 8.0.38 | Any | Any | START REPLICA doesn't start the SQL_THREAD |
115704 | 2024-07-27 13:12 | 2024-07-29 14:05 | MySQL Server: Replication | Can't repeat (273 days) | S3 | 5.7.43 | Any | Any | mysql 5.7 slave server keep lost connection |
115730 | 2024-07-31 4:32 | 2024-07-31 6:46 | MySQL Server: Replication | Verified (271 days) | S3 | 8.0.39 | Any | Any | Deadlock between OPTIMIZE TABLE and XA transaction in slave |
115450 | 2024-06-27 18:19 | 2024-08-06 1:00 | MySQL Server: Replication | No Feedback (266 days) | S1 | MySQL Ver-8.0.36 | Linux | Any | Issue with GTID replication MySQL Ver-8.0.36 | replication hangs |
115811 | 2024-08-09 18:59 | 2024-08-12 19:51 | MySQL Server: Replication | Can't repeat (259 days) | S3 | 8.0.35-27 | Ubuntu (Only Tested on Ubuntu) | Any | Replication Delay consistent at 1 second. |
115982 | 2024-09-02 13:41 | 2024-09-18 23:15 | MySQL Server: Replication | Verified (235 days) | S3 | 8.0.39 | Any | Any | The replication thread accumulates in get_default_db_collation, causing delays |
116191 | 2024-09-20 20:37 | 2024-09-22 19:51 | MySQL Server: Replication | Not a Bug (218 days) | S3 | 8.0.38 | Linux | x86 | Replication silently stops replicating when using replicate_wild_do_table |
116249 | 2024-09-27 6:48 | 2024-09-28 18:04 | MySQL Server: Replication | Verified (213 days) | S5 | all versions | Any | Any | Addressing Unfriendliness Problems in NUMA Environments |
116317 | 2024-10-09 3:16 | 2024-10-09 6:27 | MySQL Server: Replication | Verified (201 days) | S3 | 8.0.39 | Any | Any | Clone_persist_gtid thread runs even when GTID mode disabled |
116266 | 2024-09-29 14:14 | 2024-10-14 3:46 | MySQL Server: Replication | Verified (200 days) | S2 | 8.0.39 | Any | Any | Binlog record error when delimiter is set to other symbols |
116341 | 2024-10-11 3:33 | 2024-10-14 14:15 | MySQL Server: Replication | Verified (196 days) | S3 | 8.0, 8.0.39 | Any | Any | The show processlist result of the replica is inaccurate |
115976 | 2024-09-02 2:54 | 2024-10-15 7:12 | MySQL Server: Replication | Verified (238 days) | S3 | 8.0.39 | Any | Any | Inserting multiple rows into a table without a primary key fails. |
116460 | 2024-10-23 13:04 | 2024-10-24 10:44 | MySQL Server: Replication | Verified (187 days) | S5 | all versions | Any | Any | Improve the scheduling mechanism of the SQL thread to enhance the replica replay |
116312 | 2024-10-07 16:51 | 2024-11-02 20:46 | MySQL Server: Replication | Can't repeat (177 days) | S1 | 8.0.39 | Red Hat (Almalinux 8) | x86 | 8.0 replica cannot establish TLS connection with 5.7 replication source |
116564 | 2024-11-06 1:51 | 2024-11-06 12:57 | MySQL Server: Replication | Verified (173 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Replication breaks with partial_revokes when GRANT after DROP current USER. |
116753 | 2024-11-22 5:03 | 2024-11-27 8:39 | MySQL Server: Replication | Verified (152 days) | S3 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | COMPRESSION_PERCENTAGE in binary_log_transaction_compression_stats is incorrect |
116834 | 2024-12-02 7:08 | 2024-12-02 8:34 | MySQL Server: Replication | Unsupported (147 days) | S3 | 8.0.35 | Any | Any | Replication between MySQL 8.0.35 (master) and MySQL 5.7.44 (slave) fails due to an incompatibility with character sets. |
116932 | 2024-12-11 1:45 | 2024-12-13 19:06 | MySQL Server: Replication | Verified (138 days) | S3 | MySQL8.0,5.7 | Any | Any | Not update the slave_relay_log_info table in time causes replication recovery failure |
116576 | 2024-11-07 7:58 | 2024-12-29 1:00 | MySQL Server: Replication | No Feedback (121 days) | S1 | 8.0.37 | CentOS | Any | InnoDB Deadlock and Assertion Failure Leading to MySQL Crash |
117086 | 2024-12-31 9:52 | 2025-01-02 1:51 | MySQL Server: Replication | Can't repeat (116 days) | S1 | 8.0.25 | Any | Any | replace into can cause 1062 error |
116983 | 2024-12-16 7:34 | 2025-01-10 14:18 | MySQL Server: Replication | Duplicate (108 days) | S3 | 8.0.34 | Red Hat (7.9) | x86 | Master's binary log didn't apply data but write to slave's binary log |
117102 | 2025-01-03 8:48 | 2025-01-13 14:50 | MySQL Server: Replication | Closed (105 days) | S3 | 8.0.34 | Any | Any | Histogram Statistics Analysis cannot apply on standby database |
Showing 1-30 of 43 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |