[
https://issues.apache.org/jira/browse/HBASE-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645705#comment-13645705
]
Jeffrey Zhong commented on HBASE-7006:
--------------------------------------
Thanks [~anoop.hbase] for the reviewing!
{quote}
For the replay we call replay interface addded in HRS from another HRS. So all
the Mutations in that call are replay mutations.
{quote}
Agree. In fact, current implementation is this way. The replay flag is NOT
added into MutationProto protobuf message but in the Mutation class. So client
doesn't need to specify the flag while the receiving region server set the flag
so that write path code can do special logic for the replay otherwise I have to
add a new 'replay' flag input argument to all functions along the write path.
> [MTTR] Study distributed log splitting to see how we can make it faster
> -----------------------------------------------------------------------
>
> Key: HBASE-7006
> URL: https://issues.apache.org/jira/browse/HBASE-7006
> Project: HBase
> Issue Type: Bug
> Components: MTTR
> Reporter: stack
> Assignee: Jeffrey Zhong
> Priority: Critical
> Fix For: 0.95.1
>
> Attachments: hbase-7006-combined.patch, hbase-7006-combined-v1.patch,
> hbase-7006-combined-v2.patch, hbase-7006-combined-v3.patch, LogSplitting
> Comparison.pdf,
> ProposaltoimprovelogsplittingprocessregardingtoHBASE-7006-v2.pdf
>
>
> Just saw interesting issue where a cluster went down hard and 30 nodes had
> 1700 WALs to replay. Replay took almost an hour. It looks like it could run
> faster that much of the time is spent zk'ing and nn'ing.
> Putting in 0.96 so it gets a look at least. Can always punt.
--
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
