The 'Cluster Connection Test' stage verifies that the MATLAB client machine is able to communicate with the headnode running the MATLAB Job Scheduler. This tests hostname resolution (both ways), that the necessary ports are open and accepting traffic, that the mjs service is running on the headnode.
If validation fails on this stage, here are some things you can troubleshoot:
1) Verify that the headnode, specified in the cluster profile, is up and running MATLAB Job Scheduler (MJS).
You will need to verify that MJS is running on the headnode and the mjs service has been started. You can test this through the Admincenter or by running $MATLAB/toolbox/parallel/bin/nodestatus on the headnode. You can also do this through the client machine by running Admincenter and entering the headnode hostname into the 'hosts' field or by running $MATLAB/parallel/bin/nodestatus -remotehost headnode_hostname.
2) Verify that the necessary ports are open and accepting traffic on the MATLAB client and MATLAB Parallel Server cluster.
More information on the ports required for MATLAB Parallel Server can be found here:
3) Verify that your MATLAB client is able to resolve the MJS hostname.
If 'ping' is enabled on your network, you can perform a ping test by pinging the MJS hostname from the MATLAB client. Make sure to ping the MJS headnode by the hostname specified in the cluster profile.
Similarly, you will also want to make sure that your MJS headnode can ping your MATLAB client machine. In MATLAB, if you run:
It will output the hostname that the MATLAB client advertises itself by to the MJS headnode. If MJS is unable to communicate to the MATLAB client by the specified hostname, you can change the hostname the MATLAB client uses by running the following:
You will be able to change the hostname to a Fully Qualified Domain Name or an IP Address.
4) Verify the hostname of the machine running MJS resolves to the desired IP address
Verify that the hostname of the machine that MJS is running on is resolving to the correct IP Address. You can do this by pinging the hostname of the MJS headnode and comparing that to the IP Address from ifconfig, Unix, or ipconfig, Windows.
5) Verify your firewall is not blocking communication between the head node, workers and clients
Refer to the MATLAB Parallel Server firewall article:
If you are still unable to validate your cluster please contact MathWorks support:
*NOTE*: Starting in R2019a the following name changes occurred:
- MATLAB Distributed Computing Server was renamed to MATLAB Parallel Server
- mdce_def was renamed to mjs_def
- mdce binary was renamed to mjs
- mjs scripts are in $MATLAB/R20XXx/toolbox/distcomp/bin for R2019a and earlier