[HBASE-12071] Separate out thread pool for Master <-> RegionServer communication

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0, 2.0.0
• Fix Version/s: 1.0.0, 1.1.0
• Labels: reliablity
• Assignee: Stephen Yuan Jiang
• Reporter: Sudarshan Kadambi
• Created: 23/Sep/14 20:49
• Updated: 06/Apr/18 17:55
• Resolved: 08/Jan/15 22:18

Description

Over in HBASE-12028, there is a discussion about the case of a RegionServer still being alive despite all its handler threads being dead. One outcome of this is that the Master is left hanging on the RS for completion of various operations - such as region un-assignment when a table is disabled. Does it make sense to create a separate thread pool for communication between the Master and the RS? This addresses not just the case of the RPC handler threads terminating but also long-running queries or co-processor executions holding up master operations.

Issue Links

• relates to: HBASE-13351 Annotate internal MasterRpcServices methods with admin priority