Thanks Stefan.
What you are seeing is fixed in HADOOP-3232. It is different from main
problems reported in this thread. Please try 0.18.1 and see how it works.
Raghu.
Stefan Will wrote:
I'll add a comment to Jira. I haven't tried the latest version of the patch
yet, but since it's only changes the dfs client, not the datanode, I don't
see how it would help with this.
Two more things I noticed that happen when the datanodes become unresponsive
(i.e. The "Last Contact" field on the namenode keeps increasing) is:
1. The datanode process seem to be completely hung for a while, including
its Jetty web interface, sometimes for over 10 minutes.
2. The task tracker on the same machine keeps humming along, sending regular
heartbeats
To me this looks like there is some sort of temporary deadlock in the
datanode that keeps it from responding to requests. Perhaps it's the block
report being generated ?
-- Stefan
