Bug #23546 Cluster configured without any arbitration
Submitted: 23 Oct 2006 9:04 Modified: 8 Feb 2007 5:30
Reporter: Roland Bouman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S4 (Feature request)
Version:5.1.13 bk OS:na
Assigned to: justin he CPU Architecture:Any
Tags: ArbitrationRank, cluster, config.ini

[23 Oct 2006 9:04] Roland Bouman 
Description:
The cluster can be configured so that all API nodes and all of management servers have: 

ArbitrationRank=0

When one of the datanodes is taken down, the whole cluster goes down because there is no arbitrator.

It would be nice if the cluster could warn the user against this particular setup. 

How to repeat:
Please set up a cluster according to the attached config.ini file. Start the cluster, take down one of the datanodes.

Suggested fix:
Please generate a warning in the log (or the management client) so the user can identify this type of problem. 

Also, document this configuration pitfall.

Of course, if the configuration is not intentional, prevent such a configuration from being applied.
[23 Oct 2006 9:06] Roland Bouman 
2 node Config - no Arbitrator

Attachment: config.ini (application/octet-stream, text), 646 bytes.
[14 Nov 2006 2:37] 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/15284

ChangeSet@1.2320, 2006-11-14 10:28:56+08:00, Justin.He@dev3-47.dev.cn.tlan +1 -0
  BUG#23546, Cluster configured without any arbitration
[30 Jan 2007 6:09] 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/19003

ChangeSet@1.2344, 2007-01-30 13:05:40+08:00, Justin.He@dev3-240.dev.cn.tlan +1 -0
  Bug#23546, Cluster configured without any arbitration
[7 Feb 2007 17:08] Tomas Ulin 
pushed to 5.1.16
[7 Feb 2007 17:52] Tomas Ulin 
fixed in 5.1.16
not fixed in 5.0 and 4.1
[8 Feb 2007 5: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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.16 changelog.