MySQL Bugs: #52852: Each ndbd sets up more than one listening socket per transporter

Bug #52852	Each ndbd sets up more than one listening socket per transporter
Submitted:	15 Apr 2010 8:12
Reporter:	Jonathon Coombes	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.1-telco-7.0	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	cluster, ndbd, transporter

Description:
Each ndbd process sets one listening socket per transporter where it actually only needs one listening socket. 

When someone wants to connect to that node, they will always tell which node they are and thus the  correct transporter will be connected.

How to repeat:
N/A

Suggested fix:
change to only one

Posted by developer:
 
Per current design there are normally more than one listening socket setup per node. In theory only one listening socket would be necessary since each connecting client will tell which node it is and thus can connect to the correct transporter.

Setups who wish to reduce number of listening ports can use the ServerPort setting in the config.ini and thus
choose to use only the specified port.

Problem is also limited to data nodes since they don't have a dedicated well known port like the mgmt node.