I don't know. The question is mainly for the read time out: you will
connect to the ipc.Client with a read timeout of let say 10s. Server
side the implementation may do something with another server, with a
connect & read timeout of 60s. So if you have:
HBase --> live DN --> dead DN
The timeout wi
Thanks for the response, N. I could be wrong here, but since this problem is
in the HDFS client code, couldn't I set this dfs.socket.timeout in my
hbase-site.xml and it would only affect hbase connections to hdfs? I.e. we
wouldn't have to worry about affecting connections between datanodes, et
Hi Bryan,
It's a difficult question, because dfs.socket.timeout is used all over
the place in hdfs. I'm currently documenting this.
Especially:
- it's used for connections between datanodes, and not only for
connections between hdfs clients & hdfs datanodes.
- It's also used for the two types of d
Today I needed to restart one of my region servers, and did so without
gracefully shutting down the datanode. For the next 1-2 minutes we had a bunch
of failed queries from various other region servers trying to access that
datanode. Looking at the logs, I saw that they were all socket timeout
