Bug #18612 Late connection establish can lead to partitioned cluster

• Submitted: 29 Mar 2006 10:06
• Modified: 12 Apr 2006 0:30
• Reporter: Jonas Oreland
• Status: Closed
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: 4.1,5.0,5.1
• Assigned to: Jonas Oreland
• CPU Architecture: Any

[29 Mar 2006 10:06] Jonas Oreland

Description:
Use "low" value for StartPartialTimeout

e.g. 1
Running 2 node cluster (1,2)
stop 1
start 1 - let it discard connect_rep from 2
wait until sp1 is complete
connect 1 to 2
node 1 will here incorrectly continue with SR producing partitioned cluster

e.g 2
Running 4 node cluster (1,2,3,4)
stop 1
start 1 let it discard connect_rep from (2,3,4)
wait until sp1 is complete
connect 1 to 2,3,4
node 1 will here hang

How to repeat:
 

Suggested fix:

[30 Mar 2006 12:23] 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/4321

[31 Mar 2006 15:01] 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/4368

[31 Mar 2006 17: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/4373

[3 Apr 2006 9:28] 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/4404

[3 Apr 2006 10:12] 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/4407

[5 Apr 2006 12:12] 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/4494

[5 Apr 2006 21:23] 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/4525

[6 Apr 2006 9:45] 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/4546

[6 Apr 2006 14:20] 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/4564

[7 Apr 2006 8: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/4600

[9 Apr 2006 21:14] Jonas Oreland

pushed into 5.1.10

[10 Apr 2006 8:16] Jonas Oreland

pushed into 5.0.21

[10 Apr 2006 11:00] Jonas Oreland

pushed into 4.1.19

[12 Apr 2006 0:30] 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 bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 4.1.19, 5.0.21, and 5.1.10 changelogs. Closed.