[HBASE-9139] Independent timeout configuration for rpc channel between cluster nodes

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.94.10, 0.96.0
• Fix Version/s: 0.95.2, 0.94.11, 0.96.0
• Component/s: IPC/RPC, regionserver
• Hadoop Flags: Reviewed
• Assignee: Julian Zhou
• Reporter: Julian Zhou
• Created: 06/Aug/13 15:38
• Updated: 21/Aug/13 00:08
• Resolved: 13/Aug/13 04:15

Description

Default of "hbase.rpc.timeout" is 60000 ms (1 min). User sometimes
increase them to a bigger value such as 600000 ms (10 mins) for many
concurrent loading application from client. Some user share the same
hbase-site.xml for both client and server. HRegionServer
#tryRegionServerReport via rpc channel to report to live master, but
there was a window for master failover scenario. That region server
attempting to connect to master, which was just killed, backup master
took the active role immediately and put to /hbase/master, but region
server was still waiting for the rpc timeout from connecting to the dead
master. If "hbase.rpc.timeout" is too long, this master failover process
will be long due to long rpc timeout from dead master.

If so, could we separate with 2 options, "hbase.rpc.timeout" is still
for hbase client, while "hbase.rpc.internal.timeout" was for this
regionserver/master rpc channel, which could be set shorted value
without affect real client rpc timeout value?