Showing 1-30 of 484 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
88791 | 2017-12-06 15:38 | 2017-12-08 13:05 | MySQL Server: Row Based Replication ( RBR ) | Verified (2302 days) | S2 | 5.7.20 | Ubuntu | Any | Binary log for generated columncontains new value as WHERE clause, not old value |
90608 | 2018-04-24 14:43 | 2022-12-18 8:15 | MySQL Server: Row Based Replication ( RBR ) | Verified (2165 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | rpl_gtid.rpl_perfschema_applier_status_by_worker_gtid_skipped_transaction fails |
104546 | 2021-08-05 9:50 | 2024-01-30 15:57 | MySQL Server: Row Based Replication ( RBR ) | Verified (58 days) | S5 | 8.0.26 | Ubuntu (18.04.5 LTS) | x86 (Skylake-SP) | MySQL 8.0.26 single thread replication performance is slower than MySQL 5.7.35. |
113236 | 2023-11-27 17:22 | 2024-02-03 15:05 | MySQL Server: Row Based Replication ( RBR ) | Verified (121 days) | S3 | 8.0.35-0ubuntu0.22.04.1 | Ubuntu (22.04.3 LTS 5.15.0-88-generic) | x86 (.) | conflicting replica_parallel_workers spec causes parallel_mode misconfig |
80122 | 2016-01-22 22:37 | 2017-02-11 23:13 | MySQL Server: Replication | Verified (2975 days) | S2 | 5.6.25, 5.6.28 | Ubuntu | Any | semi-sync is ON (or partially so) when slaves are ON but master is OFF |
83694 | 2016-11-04 18:06 | 2016-12-18 21:55 | MySQL Server: Replication | Verified (2668 days) | S3 | 5.6.34 | Ubuntu (16.04) | Any | Replication error 1236 - claims GTIDs purged on Master but are actually present! |
87576 | 2017-08-29 9:48 | 2017-08-29 10:11 | MySQL Server: Replication | Verified (2403 days) | S3 | 5.7.19 | Ubuntu | Any | Assertion `bitmap_is _clear_all(&table->tmp_set)' failed |
89596 | 2018-02-09 4:17 | 2018-02-09 12:55 | MySQL Server: Replication | Verified (2239 days) | S3 | 8.0.4 | Ubuntu (17.10) | Any | __tls_get_addr leak on Ubuntu 17.10 |
90612 | 2018-04-24 15:19 | 2018-04-24 17:11 | MySQL Server: Replication | Verified (2165 days) | S3 | 8.0.11 | Ubuntu (14.04) | x86 | rpl_gtid.rpl_gtid_stm_drop_table test fails |
100643 | 2020-08-26 11:43 | 2020-08-28 6:11 | MySQL Server: Replication | Verified (1308 days) | S3 | 8.0.21 | Ubuntu | Any | Can't connect to MySQL with sync plugin enabled after user creation |
109290 | 2022-12-06 8:28 | 2023-01-13 6:20 | MySQL Server: Replication | Verified (440 days) | S5 | 5.7.39 | Ubuntu | x86 | WRITESET causing performance issue for replication on a replica |
78281 | 2015-08-31 2:45 | 2016-04-04 16:27 | MySQL Server: Replication | Verified (3132 days) | S3 | 5.6.16, 5.6.26 | Red Hat | Any | Big insert to MyISAM table causing SQL thread stop under 5.6 GTID |
84358 | 2016-12-28 12:47 | 2017-06-13 8:09 | MySQL Server: Replication | Verified (2646 days) | S3 | 5.7.17 | Red Hat | Any | Incorrect error reported in master server's log about slave's UUID |
93761 | 2018-12-29 2:45 | 2019-03-20 7:38 | MySQL Server: Replication | Verified (1846 days) | S2 | 5.7.22 | Red Hat (6.5) | Any | optimize table cause the slave MTS deadlock! |
80400 | 2016-02-17 1:02 | 2018-02-08 22:54 | MySQL Server: Replication | Verified (2240 days) | S3 | 5.6.29, 5.6.31, 5.6.33, 5.7.20 | Fedora (23) | Any | semisync replication - STOP SLAVE SQL_THREAD - prevents master data modification |
95235 | 2019-05-03 5:41 | 2019-05-10 1:08 | MySQL Server: Replication | Verified (1791 days) | S2 | 8.0.16 | Fedora (fc30) | x86 | ABRT:Can't generate a unique log-filename binlog.(1-999), while rotating the bin |
91822 | 2018-07-28 3:56 | 2018-07-30 10:55 | MySQL Server: Row Based Replication ( RBR ) | Verified (2068 days) | S3 | 5.6, 5.6.41, 5.5.60 | Debian | Any | incorrect datatype in RBR event when column is NULL and not explicit in query |
105400 | 2021-11-01 15:40 | 2021-11-03 7:10 | MySQL Server: Replication | Verified (876 days) | S2 | 8.0.27 | Debian | x86 | replication_sender_observe_commit_only=ON leads to break semisync replication |
83431 | 2016-10-18 18:53 | 2016-11-23 10:21 | MySQL Server: Row Based Replication ( RBR ) | Verified (2682 days) | S1 | 5.6.27.75, 5.6.34 | CentOS | Any | RBR slave's "BEGIN" binlog query event doesn't carry a session database name |
80168 | 2016-01-27 8:21 | 2018-05-21 1:44 | MySQL Server: Replication | Verified (2983 days) | S3 | 5.7.10, 5.7.12 | CentOS | Any | Assertion `get_state() >= 0' failed in sql/rpl_gtid.h:535 |
80478 | 2016-02-23 12:52 | 2016-02-24 0:10 | MySQL Server: Replication | Verified (2955 days) | S3 | 5.7.11 | CentOS | Any | Replication is failing as CASCADE clause is not working as expected in 5.7 |
80663 | 2016-03-09 4:54 | 2018-11-24 15:24 | MySQL Server: Replication | Verified (1951 days) | S3 | 5.7.10, 5.7.11, 8.0.13 | CentOS | Any | Assertion `thd->owned_gtid.is_empty()' failed in sql/rpl_gtid_state.cc:613 |
80665 | 2016-03-09 6:17 | 2016-03-09 7:18 | MySQL Server: Replication | Verified (2941 days) | S3 | 5.7.10, 5.7.11 | CentOS | Any | Assertion `thd->owned_gtid. sidno == THD::OWNED_SIDNO_ANONYMOUS' failed |
80670 | 2016-03-09 9:16 | 2016-03-09 11:17 | MySQL Server: Replication | Verified (2941 days) | S3 | 5.7.11 | CentOS | Any | Assertion `thd->variables.gtid_next.type == AUTOMATIC_GROUP' failed |
80694 | 2016-03-10 16:32 | 2016-03-11 8:44 | MySQL Server: Replication | Verified (2939 days) | S3 | 5.7.11 | CentOS | Any | Assertion `!xid->is_null() || !(thd->variables.option_bits & (1ULL<< 18))' faild |
83163 | 2016-09-27 8:07 | 2016-10-07 10:42 | MySQL Server: Replication | Verified (2729 days) | S2 | 5.7.14, 5.7.15 | CentOS (6.7) | Any | server crash after xa transaction loss transaction |
83335 | 2016-10-11 14:40 | 2016-10-12 9:10 | MySQL Server: Replication | Verified (2724 days) | S1 | 5.6.33 | CentOS | Any | replication filters fail if engine unavailable on slave, breaking replication |
83617 | 2016-10-31 8:41 | 2019-06-20 11:44 | MySQL Server: Replication | Verified (2703 days) | S2 | 5.6.27, 5.6.34 | CentOS | Any | disabling SQL mode NO_ENGINE_SUBSTITUTION doesn't work for replication |
83900 | 2016-11-21 8:04 | 2019-10-20 10:08 | MySQL Server: Replication | Verified (2435 days) | S1 | 5.7.12-log | CentOS (6.5) | Any | mysql server is crashed by binlog dump thread |
83983 | 2016-11-28 8:50 | 2019-02-18 16:38 | MySQL Server: Replication | Verified (1865 days) | S3 | 5.7.13 | CentOS (6.5) | Any | innodb fail to recover the prepared xa transaction |
Showing 1-30 of 484 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |