| Showing 1-30 of 41 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 115605 | 2024-07-16 11:27 | 2024-07-17 9:52 | MySQL Server: Replication | Verified (362 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 (350 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 (348 days) | S3 | 8.0.39 | Any | Any | Deadlock between OPTIMIZE TABLE and XA transaction in slave |
| 115811 | 2024-08-09 18:59 | 2024-08-12 19:51 | MySQL Server: Replication | Can't repeat (336 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 (312 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 (295 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 (290 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 (278 days) | S3 | 8.0.39 | Any | Any | Clone_persist_gtid thread runs even when GTID mode disabled |
| 116341 | 2024-10-11 3:33 | 2024-10-14 14:15 | MySQL Server: Replication | Verified (273 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 (315 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 (264 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 (254 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 (250 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 (229 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 (224 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 (215 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 (198 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 (193 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 (185 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 (182 days) | S3 | 8.0.34 | Any | Any | Histogram Statistics Analysis cannot apply on standby database |
| 117069 | 2024-12-30 2:09 | 2025-01-16 10:48 | MySQL Server: Replication | Can't repeat (179 days) | S3 | 8.0.34 | Red Hat (7.9) | x86 | The slave recorded the master's binary log into the binary log without applying it to the data |
| 115741 | 2024-08-01 11:13 | 2025-01-21 12:46 | MySQL Server: Replication | Verified (341 days) | S1 | 8.0 | Any | Any | Slave stops with HA_ERR_KEY_NOT_FOUND with HASH_SCAN and index used to search fo |
| 117291 | 2025-01-25 19:05 | 2025-02-01 11:56 | MySQL Server: Replication | Verified (168 days) | S3 | 8.4.3 | Any | Any | Improve migration handling of semi-sync plugins from 8.0 to 8.4 |
| 117115 | 2025-01-07 7:12 | 2025-02-10 5:50 | MySQL Server: Replication | Verified (154 days) | S3 | 5.7.44, 8.0.40 | Any | Any | The server_id of the record written to the error log by semisync is incorrect |
| 117407 | 2025-02-07 1:42 | 2025-02-10 18:03 | MySQL Server: Replication | Verified (154 days) | S3 | 8.0.38+ | Any | Any | Binlog Replication: SQL Coordinator thread hang in "waiting for handler commit" |
| 117056 | 2024-12-27 10:12 | 2025-02-25 1:00 | MySQL Server: Replication | No Feedback (140 days) | S3 | Any | Any | relay log recovery may lead to contention with explicitly called ‘start slave’ | |
| 117618 | 2025-03-04 14:31 | 2025-03-05 6:29 | MySQL Server: Replication | Verified (131 days) | S3 | 9.1, 9.2.0 | Any | Any | Erroneous warning "Combining the storage engines InnoDB and MyISAM is deprecated" |
| 117660 | 2025-03-11 4:23 | 2025-03-11 23:07 | MySQL Server: Replication | Can't repeat (125 days) | S2 | 8.4.2 | Oracle Linux (8.10) | x86 | MySQL 8.4.2: InnoDB Assertion Failure on ha_innodb.cc:11675 Due to strlen(m_remote_path) != 0 After Promoting Replica |
| 117782 | 2025-03-25 2:54 | 2025-03-25 9:42 | MySQL Server: Replication | Won't fix (111 days) | S3 | 5.7.44 | Any | Any | Semi-synchronous replication causes significant performance degradation |
| 115613 | 2024-07-16 19:33 | 2025-04-08 4:38 | MySQL Server: Replication | Verified (362 days) | S2 | 8.0.18,8.0.37, 8.0.41 | Any | Any | FLUSH PRIVILEGES on binlogless replica causes gtid_executed gap |
| Showing 1-30 of 41 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
