Bug #20683 Unhandled resource shortage in SUB_STOP_REQ causes node failure

Submitted: 25 Jun 2006 9:47 Modified: 4 Jul 2006 13:50
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S3 (Non-critical)
Version: OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[25 Jun 2006 9:47] Jonas Oreland 
Description:
Run so many sub_stop_req in parallell so that safecounter pool is full.
This error is never handled.

How to repeat:
 

Suggested fix:
[26 Jun 2006 10:16] 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/8234
[26 Jun 2006 10:31] 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/8238
[29 Jun 2006 6:22] 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/8447
[29 Jun 2006 9:53] Tomas Ulin 
pushed to 5.1.12
[4 Jul 2006 6:39] Jonas Oreland 
If using ndbapi and doing lots of parallell subscribe/unsubscribe 
  or having many mysqld starting simultanious 

this could lead to node crash
[4 Jul 2006 11:39] Jonas Oreland 
pushed into 5.0.24
[4 Jul 2006 13:50] Jon Stephens 
Documented fix in 5.0.24/5.1.12 changelogs. Closed.

Portions of this website are copyright © 2001, 2002 The PHP Group

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