Bug #47196 NDB: MaxNoOfSubscribers is not just for replication

• Submitted: 8 Sep 2009 20:34
• Modified: 15 Sep 2009 19:24
• Reporter: Andrew Hutchings
• Status: Not a Bug
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• OS: Any
• Assigned to: Jon Stephens
• CPU Architecture: Any

[8 Sep 2009 20:34] Andrew Hutchings

Description:
In http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbd-ma...

"This parameter, added in MySQL Cluster NDB 6.2.10 and MySQL Cluster NDB 6.3.7, is of interest only when using MySQL Cluster Replication."

This is not true, subscriptions are used even when replication is not in use.

How to repeat:
1. Run a cluster without replication or binary logs and 2 mysqld nodes
2. Observe the error logs for the mysqld nodes
3. ALL DUMP 8011
4. Look at the subscribers in the management node logs

[15 Sep 2009 19:24] Jon Stephens

I quite recently added this as a result of information obtained from Jonas.

Saying that there is no reason to set this parameter unless you're using Cluster Replication is *not* the same thing as saying Cluster uses subscriptions only when using replication.