[ 
https://issues.apache.org/jira/browse/HBASE-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604876#comment-13604876
 ] 

Anoop Sam John commented on HBASE-7835:
---------------------------------------

[~jeffreyz]
Nice work with the MTTR area. 
One quick question. So here you are doing a server to server call using the 
normal HTable APIs. Do we need a framework kind of thing within the RS for 
doing any RS-RS call?  During this time, client will also try using the 
handlers at this RS for their ops.
I was thinking on this area. We have different JIRAs now related to HLOG and 
its split and replay.
This one + HBASE-6772 + multi WAL...
Can we think on all together. 
For multi WAL if we have a fixed set of regions for one WAL approach, during 
one RS down Master can assign those regions(Try max) to another one RS [Region 
groups in RS]. If the corresponding HLog file also assigned to that RS, then 
for the replay it can directly do puts on the region rather than IPC.
I am just telling my thoughts around not saying these are within the scope of 
this issue :)

                
> Implementation of the log splitting without creating intermediate files 
> ------------------------------------------------------------------------
>
>                 Key: HBASE-7835
>                 URL: https://issues.apache.org/jira/browse/HBASE-7835
>             Project: HBase
>          Issue Type: Sub-task
>          Components: regionserver
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>             Fix For: 0.95.0
>
>         Attachments: hbase-7006_12.patch, hbase-7006_1.patch, 
> hbase-7006_2.patch, hbase-7006_3.patch, hbase-7006_3.patch, 
> hbase-7006_6.patch, hbase-7006_8.patch
>
>
> The sub task is to check in a separate patch for major implementation for the 
> proposal. 
> More checkins will include a new "replay" command and more metrics support.
> Thanks,
> -Jeffrey 

--
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

Reply via email to