[ https://issues.apache.org/jira/browse/HBASE-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Himanshu Vashishtha updated HBASE-6165: --------------------------------------- Attachment: HBase-6165-v1.patch I hit this problem while testing a long running replication setup. All priority handlers were blocked by replicationLog method, and cluster became unresponsive. Attached is a patch which does the following: a) Add a differnt QOS level, customQOS. Methods with this attribute will be processed by a new set of handlers. b) Adds customPriorityHandlers, a new set of handlers in Regionserver. ReplicationSink#replicateLogEntries uses this attribute. Testing: Jenkins is green. Have a long running replication setup, and its up for a few days. > Replication can overrun .META scans on cluster re-start > ------------------------------------------------------- > > Key: HBASE-6165 > URL: https://issues.apache.org/jira/browse/HBASE-6165 > Project: HBase > Issue Type: Bug > Reporter: Elliott Clark > Attachments: HBase-6165-v1.patch > > > When restarting a large set of regions on a reasonably small cluster the > replication from another cluster tied up every xceiver meaning nothing could > be onlined. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira