Bug #15401 | NDB lock problems | ||
---|---|---|---|
Submitted: | 1 Dec 2005 18:15 | Modified: | 7 Mar 2006 6:14 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 4.1.16 | OS: | various Unix |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[1 Dec 2005 18:15]
Joerg Bruehe
[7 Feb 2006 6:14]
Jonas Oreland
Can we close this?
[22 Feb 2006 15:38]
Joerg Bruehe
I did not notice this in 4.1.18, the only build we really did after I filed that bug. It is a bit surprising this should be gone in 4.1 as the push is only listed for 5.0. I do not object to closing - I will reopen it if it re-occurs in a future 4.1 build (but hope it will not).
[8 Mar 2006 0: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".