Bug #51858 ndb_new_handler does not work

Submitted:	9 Mar 2010 10:00	Modified:	16 Mar 2010 11:41
Reporter:	Magnus Blåudd	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-7.0	OS:	Any
Assigned to:	Magnus Blåudd	CPU Architecture:	Any

Description:
The MySQL Cluster data node(ndbd) installs a function pointer in the 'ndb_new_handler' global variable on startup. The purpose of this is to shutdown the ndbd if failure to allocate more memory with new occurs.

Since the code that is supposed to call the 'ndb_new_handler' function  pointer has been disabled (with #if 0) wince a long time, this functionality does not work anymore.

How to repeat:
MCI

Suggested fix:
Use the  C++ 'set_new_handler' function. 

http://www.cplusplus.com/reference/std/new/set_new_handler/

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

Pushed to 7.0.14 and 7.1.3-beta

Documented bugfix in the NDB-7.0.14 and 7.1.3 changelogs as follows:

      The internal variable ndb_new_handler, which is no longer used, 
      has been removed.

Closed.

Page generated in 0.039 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.