Bug #18966 | Change in stop/shutdown behaviour | ||
---|---|---|---|
Submitted: | 10 Apr 2006 16:07 | Modified: | 19 Jun 2006 15:39 |
Reporter: | Stewart Smith | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 5.0.21 | OS: | |
Assigned to: | Stewart Smith | CPU Architecture: | Any |
[10 Apr 2006 16:07]
Stewart Smith
[10 Apr 2006 16:08]
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/4731
[12 Apr 2006 5:15]
Stewart Smith
TODO (from review by tomas): 1. extend mgm api protocol to signal disconnect on return 2. CommandInterpreter down _nothing_, just forwards the node id's... and disconnects if signelled 3. extend mgmapi to have calls for shutdown DB only or shutdown ALL. 4. Services.cpp _only_ relays nodeids, receives stopSelf, and reports disconnect if need be 5. MgmtSrvr.cpp does all the sorting/stopping and returns stopSelf... possibly a ndb_mgm_shutdown() that accepts a node type parameter.
[25 Apr 2006 19:08]
Stewart Smith
add input from BUG#19350
[18 May 2006 11:32]
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/6564
[23 May 2006 6:24]
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/6748
[7 Jun 2006 6:21]
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/7338
[16 Jun 2006 11:42]
Stewart Smith
pushed to 5.1.12 and 5.0.23
[19 Jun 2006 15:39]
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 bugfix in 5.0.23/5.1.12 changelogs; closed.