Home > other >  Secondarynodename cannot be started
Secondarynodename cannot be started

Time:12-01


50090 port is not occupied, and secondarynamenode also configured in the configuration file
Still can't start,,, ask for help

CodePudding user response:

Netstat nao | grep -i look at 50090

CodePudding user response:

Use this method try
https://blog.csdn.net/weixin_46028577/article/details/106292265

CodePudding user response:

The master node close together, master-slave node restart together

CodePudding user response:

Besides secondynamenode above don't you have some wrong, doubt is the IP address of the hosts file you didn't match

CodePudding user response:

reference 4 floor kohane Jary response:
in addition to the above secondynamenode you don't have some wrong, doubt is the IP address of the hosts file you have paired

it is not abnormal log information

CodePudding user response:

Check the port is port conflicts which process the abutment, also do not recommend you such a deployment, production environment is to deploy the way of high availability, reference: https://blog.csdn.net/dzh284616172/article/details/107372558? Utm_source=app
  • Related