« Show Previous 50 Entries | Showing 51-100 of 182 (Edit, Save, CSV, Feed) | Show Next 50 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
68251 | 2013-02-02 1:09 | 2013-05-28 6:58 | MySQL Server: Replication | Closed (3979 days) | S3 | 5.6.9 | Any | Any | 3-way deadlock on semisync replication and binlog rotate |
68314 | 2013-02-08 13:37 | 2013-05-21 22:28 | MySQL Server: Replication | Closed (3986 days) | S2 | 5.6.10 | Any | Any | mysqldump --set-gtid-purged=AUTO does not detect if mysqld has GTIDs |
68386 | 2013-02-15 1:03 | 2013-04-03 14:50 | MySQL Server: Replication | Closed (4034 days) | S2 | mysql 5.6.10 | Any | Any | Master scans all binlogs when slave reconnects with auto positioning |
68429 | 2013-02-19 12:58 | 2014-03-29 8:16 | MySQL Server: Replication | Closed (3712 days) | S2 | 5.6.10, 5.6.14 | Linux (RHEL 6) | Any | Slave SQL: Could not execute Query event. Detailed error: ;, Error_code: 0 |
68460 | 2013-02-22 6:37 | 2014-12-19 4:59 | MySQL Server: Replication | Closed (3976 days) | S3 | 5.6.10 | Linux (CentOS release 5.8 (Final)) | Any | blocked with FLUSH TABLES WITH READ LOCK + SHOW SLAVE STATUS |
68462 | 2013-02-22 10:59 | 2014-06-26 19:07 | MySQL Server: Replication | Closed (3979 days) | S1 | 5.6.10 | Linux | Any | Server stuck in Waiting for Slave Workers to free pending events |
68485 | 2013-02-25 14:24 | 2013-04-16 6:06 | MySQL Server: Replication | Closed (4021 days) | S2 | 5.6.10 | Windows (Server 2012) | Any | relay-log-info-repository=TABLE option is not being picked up from options file |
68506 | 2013-02-27 7:23 | 2015-05-08 15:06 | MySQL Server: Replication | Closed (3991 days) | S2 | 5.6.10 | Any | Any | Got SIGSEGV on MTS recovery + SQL thread error |
68525 | 2013-02-28 15:32 | 2015-09-07 17:07 | MySQL Server: Replication | Closed (3147 days) | S1 | 5.6.10, 5.6.11 | Linux (64 bits) | Any | Error "When GTID_NEXT is set to a GTID" ROW based replication |
68569 | 2013-03-05 4:31 | 2013-05-28 6:56 | MySQL Server: Replication | Closed (3979 days) | S1 | 5.6.10 | Any | Any | deadlock with group commit |
68575 | 2013-03-05 14:49 | 2013-05-28 6:22 | MySQL Server: Replication | Closed (3979 days) | S3 | 5.6.10 | Any | Any | need protection from concurrent binlog rotate |
68599 | 2013-03-07 15:51 | 2013-06-28 14:29 | MySQL Server: Replication | Closed (3948 days) | S3 | 5.6.10 | Any | Any | Warning issued about master.info when using master-info-repository=table |
68604 | 2013-03-07 20:13 | 2013-05-07 5:31 | MySQL Server: Replication | Closed (4000 days) | S1 | 5.6.10 | Any | Any | MySQL crashes trying to start slave |
68605 | 2013-03-07 20:28 | 2013-05-06 16:20 | MySQL Server: Replication | Closed (4001 days) | S3 | 5.6.10 | Any | Any | START SLAVE after import of table-based repositories gives empty error message |
68638 | 2013-03-11 16:15 | 2013-05-28 6:17 | MySQL Server: Replication | Closed (3979 days) | S1 | 5.6.10-enterprise-commercial-advanced | Linux (3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19 12:18:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux) | Any | read_gtids_from_binlog improperly calls my_error with ER_MASTER_FATAL_ERROR_READ |
68811 | 2013-03-29 8:56 | 2013-05-07 8:03 | MySQL Server: Replication | Closed (4000 days) | S2 | 5.6.10 | Linux | Any | Replication slave stuck on simple query with user variables. |
68892 | 2013-04-09 0:05 | 2017-03-03 19:45 | MySQL Server: Replication | Closed (3865 days) | S2 | 5.6 | Any | Any | Invalid use of GRANT command breaks replication |
68953 | 2013-04-14 15:29 | 2015-10-16 14:30 | MySQL Server: Replication | Closed (3108 days) | S1 | 5.6.10, 5.6.12, 5.5.43 | Any | Any | Binlog write errors silently ignored |
69028 | 2013-04-22 0:35 | 2013-04-22 7:49 | MySQL Server: Replication | Closed (4015 days) | S3 | 5.6.11 | Any | Any | Not-So-Multithreaded-Slave |
69045 | 2013-04-24 2:01 | 2013-05-06 10:11 | MySQL Server: Replication | Closed (4001 days) | S3 | 5.6.11 | Any | Any | replication was broken while executing flush tables |
69059 | 2013-04-24 20:55 | 2015-02-11 14:37 | MySQL Server: Replication | Closed (3355 days) | S2 | 5.6.11 | Any | Any | GTIDs lack a reasonable deployment strategy |
69096 | 2013-04-29 20:52 | 2013-07-09 10:01 | MySQL Server: Replication | Closed (3937 days) | S2 | 5.6.11 | Any | Any | GTID_NEXT_LIST session variable is not visible |
69097 | 2013-04-29 22:51 | 2022-05-05 9:01 | MySQL Server: Replication | Closed (3493 days) | S2 | 5.6.11 | Any | Any | mysqld scans all binary logs on crash recovery |
69249 | 2013-05-16 4:14 | 2013-09-19 13:33 | MySQL Server: Replication | Closed (3865 days) | S3 | 5.6.11 | Any | Any | master_delay does not perform proper type checking |
69341 | 2013-05-29 0:55 | 2016-04-07 5:46 | MySQL Server: Replication | Closed (3941 days) | S5 | 5.6.11 | Any | Any | semi-sync replication is very slow with many clients |
69369 | 2013-05-31 21:45 | 2013-07-09 16:43 | MySQL Server: Replication | Closed (3937 days) | S1 | 5.6.12 | Any | Any | BGC and slave binlog rotate causes slave sql_thread to stop |
69469 | 2013-06-14 8:53 | 2013-09-19 13:27 | MySQL Server: Replication | Closed (3865 days) | S3 | 5.6.12 | Any | Any | ERROR 1729 overfills by the value of MASTER_DELAY greater than 2^31 |
69861 | 2013-07-28 9:37 | 2013-10-21 14:55 | MySQL Server: Replication | Closed (3833 days) | S2 | 5.5.32, 5.6.12/13 | Any | Any | LAST_INSERT_ID is replicated incorrectly if replication filters are used |
69898 | 2013-08-01 13:47 | 2014-07-17 17:54 | MySQL Server: Replication | Closed (3865 days) | S1 | 5.6.12 | Any (Centos 6.4) | Any | change_master() invokes ha_innobase::truncate() in a DML transaction |
69902 | 2013-08-01 18:37 | 2013-10-21 15:48 | MySQL Server: Replication | Closed (3833 days) | S1 | 5.6.12, 5.6.13 | Linux | Any | slave asserts after 5.6 upgrade |
69943 | 2013-08-07 0:46 | 2014-02-03 10:12 | MySQL Server: Replication | Closed (3824 days) | S1 | 5.6.13 | Any | Any | Transactions skipped on slave after "stop/start slave" using GTID replication |
70124 | 2013-08-22 19:39 | 2014-10-16 12:39 | MySQL Server: Replication | Closed (3537 days) | S3 | 5.6.13 | Any | Any | Timestamp and datetimes self-incompatible during replication |
70167 | 2013-08-27 19:06 | 2013-09-23 10:36 | MySQL Server: Replication | Closed (3861 days) | S3 | 5.6.13 | Any | Any | Impossible to disable MASTER_AUTO_POSITION with gtid_mode=OFF |
70218 | 2013-09-02 21:42 | 2014-03-28 19:21 | MySQL Server: Replication | Closed (3735 days) | S5 | 5.6.13 | Any | Any | Semisync master plugin with many slaves causes plugin_lock mutex contentions |
70307 | 2013-09-12 0:33 | 2015-02-12 12:37 | MySQL Server: Replication | Closed (3417 days) | S2 | 5.6.13 | Any | Any | Another deadlock on FLUSH TABLES WITH READ LOCK + SHOW SLAVE STATUS |
70327 | 2013-09-13 8:05 | 2014-09-30 13:47 | MySQL Server: Replication | Closed (3516 days) | S2 | 5.6.13 | Any | Any | Assersion error when setting future binlog file/pos with semisync |
70360 | 2013-09-17 6:38 | 2014-01-15 9:46 | MySQL Server: Replication | Closed (3747 days) | S3 | 5.6.13, 5.6.14 | Any | Any | an independent instance with semisync enabled still need ack from slave |
70391 | 2013-09-20 21:21 | 2014-08-01 15:53 | MySQL Server: Replication | Closed (3636 days) | S2 | 5.6.13, 5.6.14 | Any | Any | uninstall and install semi-sync plugin causes slaves to break |
70410 | 2013-09-24 18:49 | 2014-02-03 10:44 | MySQL Server: Replication | Closed (3796 days) | S3 | mysql 5.6.13, 5.6.14 | Any | Any | DDL queries increases rpl_semi_sync_master_yes_tx by a value of 2 |
70414 | 2013-09-25 9:31 | 2013-10-21 16:06 | MySQL Server: Replication | Closed (3833 days) | S3 | 5.6,5.7 | Any | Any | redundant code in ReplSemiSyncMaster::updateSyncHeader |
70583 | 2013-10-10 8:14 | 2014-08-06 17:08 | MySQL Server: Replication | Closed (3579 days) | S2 | 5.6.14 | Any | Any | INSERT ON DUPLICATE KEY UPDATE failing after MySQL 5.6 upgrade. |
70669 | 2013-10-20 4:25 | 2014-03-29 8:25 | MySQL Server: Replication | Closed (3704 days) | S2 | 5.6.14 | Any | Any | Slave can't continue replication after master's crash recovery |
70685 | 2013-10-22 9:53 | 2014-02-02 17:28 | MySQL Server: Replication | Closed (3810 days) | S3 | 5.6 | Any | Any | incorrectly printed binlog dump information |
70711 | 2013-10-23 18:21 | 2015-06-24 4:30 | MySQL Server: Replication | Closed (3285 days) | S3 | 5.6.14 | Any | Any | mysqlbinlog prints invalid SQL from relay logs when GTID is enabled |
70866 | 2013-11-09 20:16 | 2014-03-29 18:10 | MySQL Server: Replication | Closed (3747 days) | S3 | 5.6.14 | Any | Any | sql/rpl_slave.cc |
70922 | 2013-11-15 15:21 | 2015-01-09 7:18 | MySQL Server: Replication | Closed (3388 days) | S1 | 5.6.14 | Linux (el6.x86_64) | Any | MySQL binlog error causing slave replication to exit |
71037 | 2013-11-29 8:07 | 2014-05-27 8:52 | MySQL Server: Replication | Closed (3615 days) | S3 | 5.6.14 | Linux (rhel 6.2) | Any | can not start mysql when no Previous_gtids_log_event in the binlog |
71070 | 2013-12-04 4:05 | 2014-07-28 9:37 | MySQL Server: Replication | Closed (3628 days) | S2 | 5.6.14,5.5.18, 5.6.15 | Any | Any | kill of truncate table will lead to binary log written while rows remains |
71178 | 2013-12-18 20:57 | 2014-08-07 5:41 | MySQL Server: Replication | Closed (3572 days) | S3 | 5.6 | Any | Any | BINLOG_DUMP_NON_BLOCK disapear in MySQL 5.6 |
71197 | 2013-12-21 8:48 | 2015-01-05 2:17 | MySQL Server: Replication | Closed (3712 days) | S2 | 5.6.15, 5.6.14, 5.6.13, 5.6.16, 5.7.3 | Linux | Any | mysql slave sql thread memory leak |
« Show Previous 50 Entries | Showing 51-100 of 182 (Edit, Save, CSV, Feed) | Show Next 50 Entries » |