Bug #32913 | Multiple errors on a slave | ||
---|---|---|---|
Submitted: | 2 Dec 2007 20:23 | Modified: | 18 Aug 2008 7:32 |
Reporter: | Oleksiy Kovyrin | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.0.45 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | binlog, filters, replication, slave |
[2 Dec 2007 20:23]
Oleksiy Kovyrin
[2 Dec 2007 21:52]
Oleksiy Kovyrin
Changed replicate-*-table statements to use rewritten name of the database: Replicate_Wild_Do_Table: texts.texts, texts.word_documents, texts.word_tags, texts.word_documents_word_tags, texts.word_requests, texts.word_uploads, texts.word_users, texts.groups, texts.word_stats, texts.texts, texts.word_documents, texts.word_tags, texts.word_documents_word_tags, texts.word_requests, texts.word_uploads, texts.word_users, texts.groups,texts.word_stats And now it worked. But anyways, this looks like a bug.
[3 Dec 2007 4:15]
Oleksiy Kovyrin
Actually, it started crashing when slave caught up.
[3 Dec 2007 6:17]
Oleksiy Kovyrin
Switched new server to replicate from one of the slaves - works fine so far.
[17 Feb 2008 17:34]
Valeriy Kravchuk
Thank you for a problem report. Is this bug repeatable with a new setup? If yes, please, try to check if it is still repeatable with a newer version, 5.0.51a, and inform about the results.
[18 Mar 2008 0:02]
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".
[20 Mar 2008 10:02]
Susanne Ebrecht
Oleksiy, did I understand you right? This won't happen by using newer version? Can we close this issue?
[20 Mar 2008 15:45]
Oleksiy Kovyrin
Actually, we've tried 5.0.51 and it was crashing too. We've changed our replication scheme now and it is not crashing anymore, but I do not think that but is fixed - this is just a workaround.
[18 Aug 2008 7:32]
Sveta Smirnova
Thank you for the feedback. > We've changed our replication scheme now and it is not crashing anymore, but I do not think that but is fixed - this is just a workaround. There was not real crash, but replication stopped working. Also changing scheme is not workaround, but only correct way to do what you need if you use option replicate-rewrite-db. Only problem which I can see here is not nice error message in the error log file, although is not clear why mysqld should guess what you want to do. So I close the report as "Not a Bug".