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.

Datanodes are reading all the time without corresponding HDFS I/O activity after 5.4.5 upgrade

avatar
New Contributor

Earlier this week I upgraded to CDH 5.4.5 from 5.4.4. Since then I can see that the datanode process is constantly reading 2M/s per drive in each host (with a number of writes maybe one order of magnitude smaller), but there is no corresponding HDFS I/O activity (just the usual activity, ~40k/s) 

It seems as if nobody is actually reading anything, but the HDFS process is doing something on its own.

 

Any ideas about what could be causing this? How could I find out / diagnose what's happening?

 

Thanks!

1 ACCEPTED SOLUTION

avatar
New Contributor

After some more research we found that it wasn't a zombie spark job that was causing the resource usage. It was the HDFS blockscanner. Apparently the default configuration changed with the upgrade and it started running right after we restarted upon upgrading. We had never seen it running before and hence the mistery.

View solution in original post

4 REPLIES 4

avatar
New Contributor
Nevermind, it was a zombie spark job.

avatar
Community Manager

I am happy to see you killed off the zombies. 🙂

 

zombies.jpg

Keep the questions coming

avatar
New Contributor

After some more research we found that it wasn't a zombie spark job that was causing the resource usage. It was the HDFS blockscanner. Apparently the default configuration changed with the upgrade and it started running right after we restarted upon upgrading. We had never seen it running before and hence the mistery.

avatar
Community Manager

That makes sense but totally invalidates my Zombie sign. 🙂

 

Feel free to mark your last comment as the solution in case it can help others in the future. 

Keep the questions coming