MySQL Bugs: #80846: Specific partitioned tables always place first partition on node group 0

Bug #80846	Specific partitioned tables always place first partition on node group 0
Submitted:	24 Mar 2016 10:32	Modified:	30 Mar 2016 11:14
Reporter:	Mikael Ronström	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	7.5.1	OS:	Any
Assigned to:		CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
When creating a table with 1 partition, this partition is always created at Node Group 0.
This means that we don't spread those tables around in the system in an efficient manner.

How to repeat:
Create a number of 1-partitioned tables and use the ndbinfo memory_per_fragment to watch their distribution.

Suggested fix:
Ensure that there is no specific handling of the first partition.

Fixed in NDB 7.5.2.