stack wrote:
Jean-Adrien wrote:
lava has the same problem. But I don't think everybody does,
since the cluster could not run without disabling the timeout parameter
dfs.datanode.socket.write.timeout
Anybody made those observations ?
I haven't been paying attention of late. Thanks for bringing it up
Jean-Adrien. Lets try and figure it (I 'thought' that the timer over on
the datanode would close idle sockets but that subsequent accesses would
revive the connection but that doesn't seem to be the case going by your
hadoop posting).
For correct behavior with multiple timeouts, you need
https://issues.apache.org/jira/browse/HADOOP-3831 . I don't know why
that didn't go into 0.18.
Raghu.
St.Ack
