Bug #39154 | Unexpected row on master in system table "mysql.ndb_apply_status" | ||
---|---|---|---|
Submitted: | 1 Sep 2008 10:53 | Modified: | 25 Oct 2023 15:49 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | mysql-5.1-telco-6.3 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | mysql-5.1-telco-6.3.17 |
[1 Sep 2008 10:53]
Joerg Bruehe
[23 Oct 2008 11:29]
Jonas Oreland
i 99% sure I fixed this didnt know there was a bug, problem was the ndb_restore (with some options) put a row in ndb_apply_status and tomas reordered the tests...
[23 Oct 2008 11:30]
Jonas Oreland
btw, my triage would be D4, W5, I5
[16 Apr 2009 13:23]
Jonathan Miller
Assigned to me for verification on currently version
[25 Oct 2023 15:49]
Magnus BlÄudd
Posted by developer: Retested on 8.0.35 and there is no known problem with ndb_rpl_apply_status.test, the ndb_apply_status functionality was revisited in 8.0 when implementing WL#15455 NDB Replica threadsafe [ 50%] ndb_rpl.ndb_rpl_apply_status [ pass ] 6047