| 2017-02-28 13:09:27 |
Arturas Moskvinas |
bug |
|
|
added bug |
| 2017-02-28 13:12:24 |
Arturas Moskvinas |
description |
If "DROP TEMPORARY TABLE..." gets executed on server with GTID enabled and read_only mode enabled, then 'DROP /*!40005 TEMPORARY */ TABLE IF EXISTS `sometablename`' gets inserted in server binary log. This creates errant transaction, that other slaves in cluster might not have and can break replication if server with errant transaction gets promoted to master and this transaction is already deleted from binary logs.
Percona version tested: 5.6.35-80.0, Debian jessie
How to reproduce:
1. On any read-only server with non-privileged user execute `drop temporary table if exists sometablename`, no need to actually create temporary table before dropping.
2. Check `show master status`, you'll find new gtid generated on slave in read-only mode |
If "DROP TEMPORARY TABLE..." gets executed on server with GTID enabled and read_only mode enabled, then 'DROP /*!40005 TEMPORARY */ TABLE IF EXISTS `sometablename`' gets inserted in server binary log. This creates errant transaction, that other slaves in cluster might not have and can break replication if server with errant transaction gets promoted to master and this transaction is already deleted from binary logs.
Percona version tested: 5.6.35-80.0, Debian jessie
How to reproduce:
1. On any read-only server with non-privileged user execute "drop temporary table if exists sometablename`", no need to actually create temporary table before dropping.
2. Check `show master status`, you'll find new gtid generated on slave in read-only mode |
|
| 2017-02-28 13:13:03 |
Arturas Moskvinas |
description |
If "DROP TEMPORARY TABLE..." gets executed on server with GTID enabled and read_only mode enabled, then 'DROP /*!40005 TEMPORARY */ TABLE IF EXISTS `sometablename`' gets inserted in server binary log. This creates errant transaction, that other slaves in cluster might not have and can break replication if server with errant transaction gets promoted to master and this transaction is already deleted from binary logs.
Percona version tested: 5.6.35-80.0, Debian jessie
How to reproduce:
1. On any read-only server with non-privileged user execute "drop temporary table if exists sometablename`", no need to actually create temporary table before dropping.
2. Check `show master status`, you'll find new gtid generated on slave in read-only mode |
If "DROP TEMPORARY TABLE..." gets executed on server with GTID enabled and read_only mode enabled, then 'DROP /*!40005 TEMPORARY */ TABLE IF EXISTS `sometablename`' gets inserted in server binary log. This creates errant transaction, that other slaves in cluster might not have and can break replication if server with errant transaction gets promoted to master and this transaction is already deleted from binary logs.
Percona version tested: 5.6.35-80.0, Debian jessie
How to reproduce:
1. On any read-only server with non-privileged user execute "drop temporary table if exists `sometablename`", no need to actually create temporary table before dropping.
2. Check `show master status`, you'll find new gtid generated on slave in read-only mode |
|
| 2017-02-28 15:12:43 |
tsubasa tanaka |
bug |
|
|
added subscriber tsubasa tanaka |
| 2017-03-01 21:28:25 |
Sveta Smirnova |
attachment added |
|
test case for MTR https://bugs.launchpad.net/percona-server/+bug/1668602/+attachment/4829318/+files/rpl_bug1668602.test |
|
| 2017-03-01 21:29:31 |
Sveta Smirnova |
attachment added |
|
Option file for master, create same one for the slave https://bugs.launchpad.net/percona-server/+bug/1668602/+attachment/4829319/+files/rpl_bug1668602-master.opt |
|
| 2017-03-01 21:29:54 |
Sveta Smirnova |
percona-server: status |
New |
Confirmed |
|
| 2017-03-01 21:30:01 |
Sveta Smirnova |
nominated for series |
|
percona-server/5.6 |
|
| 2017-03-01 21:30:01 |
Sveta Smirnova |
bug task added |
|
percona-server/5.6 |
|
| 2017-03-01 21:30:01 |
Sveta Smirnova |
nominated for series |
|
percona-server/5.7 |
|
| 2017-03-01 21:30:01 |
Sveta Smirnova |
bug task added |
|
percona-server/5.7 |
|
| 2017-03-01 21:30:09 |
Sveta Smirnova |
percona-server/5.6: status |
New |
Confirmed |
|
| 2017-03-01 21:33:22 |
Sveta Smirnova |
bug watch added |
|
http://bugs.mysql.com/bug.php?id=85258 |
|
| 2017-03-01 21:33:22 |
Sveta Smirnova |
bug task added |
|
mysql-server |
|
| 2017-03-01 23:28:14 |
Ovais Tariq |
bug |
|
|
added subscriber Ovais Tariq |
| 2017-03-02 03:36:45 |
Laurynas Biveinis |
percona-server/5.6: importance |
Undecided |
Medium |
|
| 2017-03-02 03:36:47 |
Laurynas Biveinis |
percona-server/5.7: importance |
Undecided |
Medium |
|
| 2017-03-02 03:36:51 |
Laurynas Biveinis |
percona-server/5.6: status |
Confirmed |
Triaged |
|
| 2017-03-02 03:36:52 |
Laurynas Biveinis |
percona-server/5.7: status |
Confirmed |
Triaged |
|
| 2017-03-02 03:36:59 |
Laurynas Biveinis |
tags |
|
upstream |
|
| 2017-03-08 04:15:12 |
Laurynas Biveinis |
percona-server/5.6: assignee |
|
Laurynas Biveinis (laurynas-biveinis) |
|
| 2017-03-08 04:15:15 |
Laurynas Biveinis |
percona-server/5.7: assignee |
|
Laurynas Biveinis (laurynas-biveinis) |
|
| 2017-03-08 04:15:18 |
Laurynas Biveinis |
percona-server/5.6: status |
Triaged |
In Progress |
|
| 2017-03-15 14:46:34 |
Laurynas Biveinis |
percona-server/5.6: status |
In Progress |
Fix Committed |
|
| 2017-03-15 14:46:37 |
Laurynas Biveinis |
percona-server/5.7: status |
Triaged |
In Progress |
|
| 2017-03-16 11:05:30 |
Laurynas Biveinis |
percona-server/5.7: status |
In Progress |
Fix Committed |
|
| 2017-03-20 13:44:45 |
Laurynas Biveinis |
percona-server/5.6: milestone |
|
5.6.36-81.0 |
|
| 2017-03-20 13:44:46 |
Laurynas Biveinis |
percona-server/5.7: milestone |
|
5.7.18-13 |
|
| 2017-03-20 13:44:50 |
Laurynas Biveinis |
percona-server/5.7: status |
Fix Committed |
Fix Released |
|
| 2017-03-20 13:44:52 |
Laurynas Biveinis |
percona-server/5.6: status |
Fix Committed |
Fix Released |
|
