[
https://issues.apache.org/jira/browse/HBASE-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-6550:
-------------------------
Fix Version/s: (was: 0.95.0)
0.94.2
Fix up after bulk move overwrote some 0.94.2 fix versions w/ 0.95.0 (Noticed by
Lars Hofhansl)
> Refactoring ReplicationSink to make it more responsive of cluster health
> ------------------------------------------------------------------------
>
> Key: HBASE-6550
> URL: https://issues.apache.org/jira/browse/HBASE-6550
> Project: HBase
> Issue Type: New Feature
> Components: Replication
> Reporter: Himanshu Vashishtha
> Assignee: Himanshu Vashishtha
> Fix For: 0.94.2
>
> Attachments: 6550-havealook.txt, HBase-6550-0.94.patch,
> HBase-6550-0.94-v2.patch, HBase-6550-0.94-v3.patch, HBase-6550.patch,
> HBase-6550-v1.patch, HBase-6550-v3.patch, HBase-6550-v4.patch,
> HBase-6550-v5.patch, HBase-6550-v6.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
