Bug #33206 signal not reset properly in ndb

Submitted:	13 Dec 2007 11:02	Modified:	14 Dec 2007 20:21
Reporter:	Tomas Ulin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	4.1->	OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
observed as a hang when using events in 5.1... but could result in various errors

How to repeat:
.

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/39884

ChangeSet@1.2577, 2007-12-13 12:03:11+01:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug #33206  	signal not reset properly in ndb

Pushed into 5.1.23-rc

Pushed into 5.0.56

Pushed into 6.0.5-alpha

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 in the 5.0.56, 5.2.23, and 6.0.5 changelogs as:

        An improperly reset internal signal was observed as a hang when
        using events in the NDB API but could result in various errors.

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.