Bug #25487 | deleting ndb_cluster_connection object takes long time | ||
---|---|---|---|
Submitted: | 9 Jan 2007 5:30 | Modified: | 25 Jan 2007 8:08 |
Reporter: | Stewart Smith | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: NDB API | Severity: | S3 (Non-critical) |
Version: | 5.0.34,5.1.14 | OS: | |
Assigned to: | Stewart Smith | CPU Architecture: | Any |
[9 Jan 2007 5:30]
Stewart Smith
[9 Jan 2007 5:54]
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/17756 ChangeSet@1.2356, 2007-01-09 16:54:34+11:00, stewart@willster.(none) +6 -0 Bug #25487 deleting ndb_cluster_connection object takes long time aim is to: a) if set_connect_timeout called, timeout connect attempt (for retry on next call) after timeout period b) preserve existing blocking behaviour otherwise (for, e.g. mgmapi) Related to customer issue with long time deleting ndb_cluster_connection object. believe we're hanging on the connect(2) call until timeout (when we then realise we should exit the thread).
[23 Jan 2007 6: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/18600 ChangeSet@1.2367, 2007-01-23 17:07:09+11:00, stewart@willster.(none) +5 -0 Bug #25487 deleting ndb_cluster_connection object takes long time aim is to: a) if set_connect_timeout called, timeout connect attempt (for retry on next call) after timeout period b) preserve existing blocking behaviour otherwise (for, e.g. mgmapi) Related to customer issue with long time deleting ndb_cluster_connection object. believe we're hanging on the connect(2) call until timeout (when we then realise we should exit the thread).
[23 Jan 2007 14:23]
Stewart Smith
approved by tomas and jonas, pushed to 5.0-ndb and 5.1-ndb
[24 Jan 2007 2:04]
Tomas Ulin
pushed to 5.1.15
[24 Jan 2007 7:53]
Tomas Ulin
pushed to 5.0.36
[25 Jan 2007 8:08]
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 bug fix. More information about accessing the source trees is available at http://dev.mysql.com/doc/en/installing-source.html Documented bugfix in 5.0.36 and 5.1.15 changelogs.