[HBASE-8729] distributedLogReplay may hang during chained region server failure

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.0, 0.95.2
• Component/s: MTTR
• Hadoop Flags: Reviewed
• Assignee: Jeffrey Zhong
• Reporter: Jeffrey Zhong
• Created: 11/Jun/13 07:05
• Updated: 23/Sep/13 19:22
• Resolved: 05/Jul/13 08:46

Description

In a test, half cluster(in terms of region servers) was down and some log replay had incurred chained RS failures(receiving RS of a log replay failed again).

Since by default, we only allow 3 concurrent SSH handlers(controlled by

this.executorService.startExecutorService(ExecutorType.MASTER_SERVER_OPERATIONS,conf.getInt("hbase.master.executor.serverops.threads", 3));

).

If all 3 SSH handlers are doing logReplay(blocking call) and one of receiving RS fails again then logReplay will hang because regions of the newly failed RS can't be re-assigned to another live RS(no ssh handler will be processed due to max threads setting) and existing log replay will keep routing replay traffic to the dead RS.

The fix is to submit logReplay work into a separate type of executor queue in order not to block SSH region assignment so that logReplay can route traffic to a live RS after retries and move forward.

Issue Links

• is related to: HBASE-7006 [MTTR] Improve Region Server Recovery Time - Distributed Log Replay