MySQL Bugs: #89846: NDB FULLY_REPLICATED does not need FOR_RA_BY_NODE or FOR_RA_BY

Bug #89846	NDB FULLY_REPLICATED does not need FOR_RA_BY_NODE or FOR_RA_BY_LDM
Submitted:	28 Feb 2018 12:40	Modified:	29 Mar 2018 6:37
Reporter:	Ted Wennmark	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Documentation	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
MySQL Cluster 7.5 feature NDB FULLY_REPLICATED does not require partition balance to be FOR_RA_BY_NODE or FOR_RA_BY_LDM.

This is mentioned here: https://dev.mysql.com/doc/refman/5.7/en/create-table-ndb-table-comment-options.html

FULLY_REPLICATED controls whether the table is fully replicated, that is, whether each data node has a complete copy of the table. To enable full replication of the table, use FULLY_REPLICATED=1. You must also set (or have already set) the table's PARTITION_BALANCE to either one of FOR_RA_BY_NODE or FOR_RA_BY_LDM in order for this to work.

How to repeat:
drop database IF EXISTS ted;
create database ted;
use ted;

create table test (
   id int primary key auto_increment,
   name varchar(32),
   address varchar(32),
   age int,
   index (name)
)engine=ndb COMMENT="NDB_TABLE=FULLY_REPLICATED=1";

mysql> select  doi.fq_name as table_name, tds.tab_partitions, tds.tab_fragments,ti.read_backup, ti.fully_replicated,ti.partition_balance from  ndbinfo.table_info ti, ndbinfo.dict_obj_info doi, ndbinfo.table_distribution_status tds where ti.table_id=doi.id and tds.table_id=doi.id and fq_name='ted/def/test'\G
*************************** 1. row ***************************
       table_name: ted/def/test
   tab_partitions: 4
    tab_fragments: 4
      read_backup: 1
 fully_replicated: 1
partition_balance: FOR_RP_BY_LDM
1 row in set (0,03 sec)

Default partition_balance is actually FOR_RP_BY_LDM is I only specify "COMMENT="NDB_TABLE=FULLY_REPLICATED=1"; as seen above.

Hi,

Thanks for the report, you are right, no specific PARTITION_BALANCE is or have been needed, the default FOR_RP_BY_LDM is ok. Will inform the doc team to fix the doc.

kind regards
Bogdan

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.

Fixed in mysqldoc rev 56662.

Closed.