[HBASE-16345] RpcRetryingCallerWithReadReplicas#call() should catch some RegionServer Exceptions

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0, 1.0.3, 1.4.0, 1.2.3, 1.1.7, 2.0.0
• Fix Version/s: 1.4.0, 2.0.0
• Component/s: Client
• Assignee: Hua Xiang
• Reporter: Hua Xiang
• Created: 03/Aug/16 08:33
• Updated: 15/Jun/17 17:41
• Resolved: 14/Nov/16 21:40

Description

Update for the description. Debugged more at this front based on the comments from Enis.

The cause is that for the primary replica, if its retry is exhausted too fast, f.get() [1] returns ExecutionException. This Exception needs to be ignored and continue with the replicas.
The other issue is that after adding calls for the replicas, if the first completed task gets ExecutionException (due to the retry exhausted), it throws the exception to the client[2].
In this case, it needs to loop through these tasks, waiting for the success one. If no one succeeds, throw exception.

Similar for the scan as well

[1] https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerWithReadReplicas.java#L197

[2] https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCallerWithReadReplicas.java#L219

Issue Links

• Is contained by: HBASE-18223 Track the effort to improve/bug fix read replica feature
• links to: Review Board (master)