Bug #34445 Incorrectly dimensioned pool, could cause cluster-failure when doing +3 to

Submitted: 10 Feb 2008 12:03 Modified: 10 Mar 2008 17:09
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:>6.3.8 OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[10 Feb 2008 12:03] Jonas Oreland
Description:
Incorrectly dimensioned pool, could cause cluster-failure when doing more than
3 parallel take-overs (node restart or take-over during system restart)

The higher the parallelism, the greater the risk

How to repeat:
run testNodeRestart -n pnr with more than 6 nodes
[10 Feb 2008 12:05] 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/41986

ChangeSet@1.2874, 2008-02-10 13:06:21+01:00, jonas@perch.ndb.mysql.com +3 -0
  ndb - bug#34445
    Incorrectly dimensioned pool, could cause cluster-failure when doing
    more than 3 parallel take-overs (node restart or take-over during system restart)
  
    Move usage of getParam into separate function (called by BLOCK_CONSTRUCTOR) so that 
      it's called on correct block
[10 Feb 2008 12:08] Jonas Oreland
pushed to telco-6.x (>=3)
[12 Feb 2008 15:45] Jon Stephens
Documented bugfix in 5.1.23-ndb-6.3.9 changelog as follows:

        Cluster failures could sometimes occur when performing
        more than three parallel takeovers during node restarts or
        system restarts.

Left in PQ pending further merges.
[10 Mar 2008 13:11] Tomas Ulin
this bug is only in telco 6.3 and upwards
[10 Mar 2008 17:09] Jon Stephens
Updated changelog entry per note from Tomas.

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

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.