1. Destination of migration could not be found!------ This is just a warning which does not seem to cause the issue. Also I can see hazelcaste exception please correct it if required and do a node by node restart with clear cache of temp folder.
2. For second issue If the auto-discovery is enabled then you have to truncate these table pegadata.pr_sys_statusnodes,
if auto-discovery is not enabled then add host IP manually in jmx configuration
Replace public IP with your instance IP respective JMX port
3.The third issue is due to the exception that is there because of hazelcast exception and it is filling up the logs.