Sounds like a boot storm scenario, where you might be exhausting node resources when you attempt so many mounts at a time.
You could look at the event log in the CLI of ONTAP (event log show) and see if you're getting any connection errors or NFS errors.
If this is NFSv3, try adding "tcp" to the mount options to ensure that the connections are closed properly when mounts occur. Some of the ancillary stuff in NFS uses UDP, which will time out on its own in the server, but will eat up connection resources in the meantime.
If this is NFSv4, see if you're hitting any storepool limits:
NFSv4 Storepool - Resolution guide - NetApp Knowledge Base
Also, as a best practice, set up at least 1 IP address per node in the SVM, set up a DNS round robin (ie, A/AAAA records with the same hostname but different IP addresses) and then have the mounts try the FQDN to round robin those connections.