Bug #57949 | angel fails to spawn ndbd on Windows | ||
---|---|---|---|
Submitted: | 3 Nov 2010 9:48 | Modified: | 5 Nov 2010 22:28 |
Reporter: | Magnus Blåudd | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 7.0.20 | OS: | Windows |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
[3 Nov 2010 9:48]
Magnus Blåudd
[3 Nov 2010 10:51]
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/122639
[3 Nov 2010 15:48]
Magnus Blåudd
Pushed to 7.0.20 and 7.1.9
[3 Nov 2010 15:49]
Jon Stephens
Per Magnus on IRC: Fix appears in 7.0+, not in 6.3.
[5 Nov 2010 22:28]
Jon Stephens
Documented in the NDB7.0.20 and 7.1.9 changelogs, as follows: On Windows, the angel process which monitors and (when necessary) restarts the data node process failed to spawn a new worker in some circumstances where the arguments vector contained extra items placed at its beginning. This could occur when ndbd.exe or ndbmtd.exe was located such that the path contained one or more spaces. Closed.