[HBASE-6550] Refactoring ReplicationSink to make it more responsive of cluster health

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.94.2
• Component/s: Replication
• Hadoop Flags: Reviewed
• Assignee: Himanshu Vashishtha
• Reporter: Himanshu Vashishtha
• Created: 09/Aug/12 17:31
• Updated: 07/Apr/13 05:17
• Resolved: 30/Aug/12 23:39

Description

ReplicationSink replicates the WALEdits in the local cluster. It uses native HBase client to insert the mutations. Sometime, it takes a while to process it (may be due to region splitting, gc pause, etc) and it undergoes the retrial phase.
It has two repercussions:
a) The regionserver handler which is serving the request (till now, a priority handler) is blocked for this period.
b) The caller may get timed out and it will retry it anyway, but the handler serving the ReplicationSink requests is still working.

Refactoring ReplicationSink to have the following features:
a) Making it more configurable (have its own number of retrial limit, connection timeout, etc)
b) Add a fail fast behavior so that it bails out in case caller is timedout, or any exception in processing the mutation batch.