Bug #81744 | DROP TABLE IF EXISTS brake replication master-slave replication | ||
---|---|---|---|
Submitted: | 7 Jun 2016 5:28 | Modified: | 7 Jul 2016 7:53 |
Reporter: | ATUL SINGH | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.10 | OS: | CentOS (6.5) |
Assigned to: | CPU Architecture: | Any |
[7 Jun 2016 5:28]
ATUL SINGH
[7 Jun 2016 7:53]
MySQL Verification Team
Hello ATUL, Thank you for the report. This issue is most likely fixed after Bug #77684, could you please check with latest GA build i.e 5.7.13 and report us back if you are still seeing the issue along with conf file used on master/slave, exact test case( table DDL, subset of data and statement which causing issue). Thanks, Umesh
[8 Jul 2016 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".