Showing 1-30 of 53 (Edit, Save, CSV, Feed) Show Next 30 Entries »
ID# Date Updated Type Status Sev Version OS CPU Summary
1134892023-12-22
7:43
2024-01-04
3:36
MySQL Server: ReplicationCan't repeat
(335 days)
S35.7.26 5.7.36 5.7.44AnyAnygtid_executed table lost the last binlog gtids
1135392024-01-02
19:44
2024-02-13
1:00
MySQL Server: ReplicationNo Feedback
(296 days)
S35.7AnyAnyBinlog replication in single threaded doesn't update transactional info table
1135642024-01-05
10:49
2024-11-07
14:39
MySQL Server: ReplicationVerified
(176 days)
S58.0Any (>= glibc 2.25 )Anywrite-only mode performance decreases by 15% in heavy workload
1136342024-01-12
17:33
2024-01-14
9:16
MySQL Server: ReplicationVerified
(325 days)
S38.0AnyAnyContribution: fix plugin semisync find minAck bug
1136632024-01-17
11:37
2024-01-17
12:04
MySQL Server: ReplicationCan't repeat
(322 days)
S38.0.32CentOSx86Crash occurs when applying binlog_transaction_dependency_tracking to slave node.
1137072024-01-22
11:52
2024-01-22
12:04
MySQL Server: ReplicationVerified
(317 days)
S38.3.0, 8.0.36AnyAnyreplication stops after updating geometry column
1137272024-01-23
14:34
2024-01-26
6:39
MySQL Server: ReplicationVerified
(313 days)
S18.0.19+AnyAnyGTID Replica stalls completely when log_slave_updates=0 and a local DDL executed
1137692024-01-26
2:42
2024-03-01
1:00
MySQL Server: ReplicationNo Feedback
(279 days)
S35.7.44AnyAnyGenerated column json binary format is incorrent
1138132024-01-31
2:26
2024-02-07
8:24
MySQL Server: ReplicationVerified
(308 days)
S3MySQL8.0,8.0.36AnyAnySemisync will abort due to wrong transaction binlog postion comparison
1138142024-01-31
2:42
2024-01-31
13:16
MySQL Server: ReplicationVerified
(308 days)
S3MySQL8.0,5.7AnyAnyThe Rpl_semi_sync_master_yes_tx and Rpl_semi_sync_master_no_tx are inaccurate
1140742024-02-21
8:35
2024-02-27
14:20
MySQL Server: ReplicationVerified
(287 days)
S58.0.32AnyAnyoptimize for Writeset_trx_dependency_tracker::get_dependency
1141172024-02-26
10:13
2024-03-21
6:20
MySQL Server: ReplicationUnsupported
(258 days)
S35.7.24CentOS (7.8)x86 (Intel(R) Xeon(R),2 cpu,2.5GHZ,)Slave Abnormally stoped out of io thread error:Unknown error noted
1141252024-02-26
15:51
2024-02-27
13:37
MySQL Server: ReplicationVerified
(282 days)
S38.0.35,8.0.36CentOS (7.9)x86Parameter set by SET PERSIST is not set to replication threads when restart
1141982024-03-04
4:21
2024-03-07
7:23
MySQL Server: ReplicationVerified
(273 days)
S38.0.35, 8.0.36AnyAnyUsing PERSIST on binlog_transaction_compression partially compresses binary log
1142732024-03-08
2:04
2024-04-09
1:00
MySQL Server: ReplicationNo Feedback
(240 days)
S3MySQL8.0.22 to 8.0.33AnyAnyturn on the binlog compression and load large data to server will cause oom
1143102024-03-12
4:14
2024-03-19
7:24
MySQL Server: ReplicationVerified
(267 days)
S38.0.33AnyAnyMaster_compression_algorithm output is wrong
1143612024-03-15
1:53
2024-08-14
9:34
MySQL Server: ReplicationVerified
(261 days)
S58.0AnyAnyUnaligned Delegate's lock reduces performance
1144722024-03-25
7:17
2024-03-25
7:20
MySQL Server: ReplicationVerified
(254 days)
S3V8.0AnyAnyMySQL replica encounter error when master and replica innodb_strict_mode=OFF
1145112024-03-29
7:05
2024-04-02
9:58
MySQL Server: ReplicationNot a Bug
(246 days)
S3MySQL8.0.22AnyAnyTurn on binlog compression and read binlog generate by big transaction cause oom
1145882024-04-09
1:34
2024-04-09
14:49
MySQL Server: ReplicationVerified
(239 days)
S38.0AnyAnySetting the instance to super-read-only still allows the flush priveleges comman
1146942024-04-19
2:24
2024-05-07
8:08
MySQL Server: ReplicationVerified
(211 days)
S38.0.34Any (CentOS Linux release 7.6.1810 (Core) )Anybinlog_transaction_compression not effect on slave
1146992024-04-19
5:16
2024-04-22
9:35
MySQL Server: ReplicationVerified
(226 days)
S18.0.36AnyAnyInconsistent XA between master and slave if crash
1147762024-04-25
7:00
2024-04-25
7:51
MySQL Server: ReplicationDuplicate
(223 days)
S38.0.32AnyAnymysqlbinlog cannot print geometry correct
1149342024-05-09
7:33
2024-06-05
2:06
MySQL Server: ReplicationCan't repeat
(182 days)
S35.7.44AnyAnyIn Heavy workload, it degenerates to use single thread replication in fact
1150242024-05-16
5:04
2024-05-17
20:46
MySQL Server: ReplicationCan't repeat
(201 days)
S28.0.33Linux (Rocky Linux release 8.9)AnyMySQL Crash occurs during MySQL Replication stop process
1151892024-05-31
19:54
2024-06-10
23:10
MySQL Server: ReplicationVerified
(182 days)
S38.4.0, 8.0.37AnyAnyP_S Digest table unexpectedly reports created database on replica
1152032024-06-03
17:34
2024-06-10
23:09
MySQL Server: ReplicationVerified
(184 days)
S38.4.0, 8.0.37AnyAnyEmpty "use ;" on replica in slow query log file.
1153102024-06-12
20:33
2024-06-17
8:00
MySQL Server: ReplicationVerified
(170 days)
S28.4.0AnyAnyGranting SET_USER_ID breaks replication from 8.0 to 8.4.
1153442024-06-14
23:49
2024-06-17
8:02
MySQL Server: ReplicationVerified
(170 days)
S38.4.0AnyAnyTerminology update for mysql internal tables
1153552024-06-17
8:58
2024-06-17
14:55
MySQL Server: ReplicationVerified
(170 days)
S38.4, 8.0.37AnyAnySQLs in procedure make replication throw error
  Showing 1-30 of 53 (Edit, Save, CSV, Feed) Show Next 30 Entries »