| Bug #15587 | NF during CopyFragReq can lead to repeated NF during NR | ||
|---|---|---|---|
| Submitted: | 8 Dec 2005 14:43 | Modified: | 14 Dec 2005 19:28 |
| Reporter: | Jonas Oreland | ||
| Status: | Closed | ||
| Category: | Server: Cluster | Severity: | S3 (Non-critical) |
| Version: | 4.1,5.0,5.1 | OS: | |
| Assigned to: | Jonas Oreland | Target Version: | |
[8 Dec 2005 15:25]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/33170
[8 Dec 2005 15:27]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/33171
[13 Dec 2005 14:57]
Jonas Oreland
pushed into 5.0.18 (not yet in 4.1)
[14 Dec 2005 7:34]
Jonas Oreland
pushed into 4.1.17
[14 Dec 2005 19:28]
Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
Additional info:
Documented fix in 4.1.17 and 5.0.18 changelogs. Closed.
[6 Mar 2007 11:04]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/21213 ChangeSet@1.2109, 2007-03-06 11:04:00+01:00, jonas@perch.ndb.mysql.com +2 -0 ndb - wl2325-5.0 bug#15587 fix incorrect merge (test prg only)
Description: NF during CopyFrag leads to node not removed from activeNodes array. When it later restart, it will be added again. Which will be detected in LQH during NR (if running transactions) as NextReplicaNode will be ==ownNodeId How to repeat: Suggested fix: