Bug #19656 | MySQL Error log flooded with [ERROR] NDB Binlog: Duplicate key on write or upda | ||
---|---|---|---|
Submitted: | 9 May 2006 21:55 | Modified: | 23 May 2006 14:43 |
Reporter: | Jonathan Miller | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.1.11 | OS: | |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
[9 May 2006 21:55]
Jonathan Miller
[10 May 2006 6:24]
Jonas Oreland
I get this when restarting cluster initial, wo/ stopping mysqld and doing mysqld_install_db Did you do this?
[10 May 2006 13:11]
Tomas Ulin
if cluster is restarted --initial, we unfortunately currently have no way of detecting this... anyways... a --initial start resets the gci's... hence you are getting the "duplicate key, 121" in binlog index, you have to do a "reset master", to clear the binlog_index, and to get rid of is
[10 May 2006 13:18]
Jonathan Miller
In either case, flooding the error log is not a good way to handel this one or two message would be fine. Maybe even with the explination you just gave me. But we should not have a log full of the same error message.
[23 May 2006 14:43]
Jon Stephens
This is already documented. See http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-replication-issues.html