Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 05-18-2016 08:45 AM
Even when a host crashes, can I know on which port NAMENODE was listening on the crashed host ?
Created 05-18-2016 08:51 AM
Login to Ambari - Click Services-> HDFS serivce->Summary->Click on Namenode <- a new page will open which will display hostname on top on which namenode is running. Same for ZKFC
2. ps -aef |grep nameode <-capture the pid from here [for eg say it is 3490
then do netstat for that pid to get the port -
netstat taupen |grep <pid/3490>
The 4th column in netstat o/p shows ipaddress:port no.
Difficult for namenode port even if service crash.
You should check namenode conf file for port on which namenode service will always start - /etc/hadoop/confhdfs-site.xml [port 8020,50070]
Created 05-18-2016 08:51 AM
Login to Ambari - Click Services-> HDFS serivce->Summary->Click on Namenode <- a new page will open which will display hostname on top on which namenode is running. Same for ZKFC
2. ps -aef |grep nameode <-capture the pid from here [for eg say it is 3490
then do netstat for that pid to get the port -
netstat taupen |grep <pid/3490>
The 4th column in netstat o/p shows ipaddress:port no.
Difficult for namenode port even if service crash.
You should check namenode conf file for port on which namenode service will always start - /etc/hadoop/confhdfs-site.xml [port 8020,50070]
Created 05-18-2016 09:19 AM
@Sagar Shimpi ThanksMan, it helped 🙂
For all two NAMENODE in my cluster I can initialize a ini file with component and port number, and later on after a node crashes, I can use this ini file for further recovery process...
Thanks again 🙂