[ https://issues.apache.org/jira/browse/HBASE-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048701#comment-13048701 ]
Jason Rutherglen commented on HBASE-2357: ----------------------------------------- Sounds like the basic design is there are N slaves that connect to one master using a socket based protocol. There will be a socket connection open per-region per slave. The Coprocessor will place edits into a per region queue, and a separate thread will write the edits onto the slave socket connections. How will this look in Zookeeper? Or should it function in the HMaster? > Coprocessors: Add read-only region replicas (slaves) for availability and > fast region recovery > ---------------------------------------------------------------------------------------------- > > Key: HBASE-2357 > URL: https://issues.apache.org/jira/browse/HBASE-2357 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver > Reporter: Todd Lipcon > Assignee: Andrew Purtell > > I dont plan on working on this in the short term, but the idea is to extend > region ownership to have two modes. Each region has one primary region server > and N slave region servers. The slaves would follow the master (probably by > streaming the relevant HLog entries directly from it) and be able to serve > stale reads. The benefit is twofold: (a) provides the ability to spread read > load, (b) enables very fast region failover/rebalance since the memstore is > already nearly up to date on the slave RS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira