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]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Version mismatch of datanode after HDP upgrade.

avatar
Expert Contributor

I have upgrade HDP from 2.3.4.0 to 2.4.0.0 and all it's ok, but one of the two NameNode tell me:

3445-cattura.png

I have only 3 datanode and I checked the running processes on all: they are to the version 2.4.0

1 ACCEPTED SOLUTION

avatar
Master Guru

@Davide Isoardi

Can you please try below command:

hdfs dfsadmin -fs hdfs://<problematic-nn-fqdn>:8020 -refreshNodes

Note - Please run above command by hdfs user.

Also, Can you please check datanode logs on hdpslave04 and see if you get anything in there.

View solution in original post

5 REPLIES 5

avatar

Hi @Davide Isoardi that's particularly strange! Does this state still persist after restarting (or indeed stopping/starting) the services?

Let us know how it goes!

avatar
Expert Contributor

This state still persist after restart of all HDFS component. I didn't try to stop and start the datanode, but it's strange why I have 3 datanode and not 4. Also shows me the following state:

3446-cattura.png

avatar
Master Guru

@Davide Isoardi

Can you please try below command:

hdfs dfsadmin -fs hdfs://<problematic-nn-fqdn>:8020 -refreshNodes

Note - Please run above command by hdfs user.

Also, Can you please check datanode logs on hdpslave04 and see if you get anything in there.

avatar
Expert Contributor

I have run this command and stop and star the problematic nameNode; Now it's all ok.

Thank you

avatar
Master Guru

@Davide Isoardi - You are welcome! 🙂