Bug #26476 | DUMP 2502 (TcDumpAllScanRec) dumps the last record twice | ||
---|---|---|---|
Submitted: | 19 Feb 2007 8:13 | ||
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1 | OS: | Linux (linux) |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.1bk |
[19 Feb 2007 8:13]
Hartmut Holzgraefe
[20 Feb 2007 14:08]
Jonas Oreland
please just add the return I also read your page, reason for not a simple loop is the following 1) ndbd is single threaded, a single loops blocks _all_ transaction therefore we manually timeslice, by sending signal to self 2) a single loop would/will fill sendbuffer quite rapidly and whould most likely cause node failure. i think the current impl. that you're looking at might have this behavior, i.e that it's not carefully enough timesliced... 3) fyi i added per customer request a set of dump commands that was carefully written that enabled dumping of transaction/operations for debugging lock problems however, this has not hit mainline... /Jonas