- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Datanodes are reading all the time without corresponding HDFS I/O activity after 5.4.5 upgrade
Created on ‎08-20-2015 08:54 AM - edited ‎09-16-2022 02:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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!
Created ‎10-09-2015 05:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Created ‎08-24-2015 06:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Created ‎08-24-2015 07:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am happy to see you killed off the zombies. 🙂
Cy Jervis, Manager, Community Program
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Created ‎10-09-2015 05:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Created ‎10-09-2015 05:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Cy Jervis, Manager, Community Program
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
