[
https://issues.apache.org/jira/browse/HBASE-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093444#comment-14093444
]
Enis Soztutar commented on HBASE-11567:
---------------------------------------
I would also say that logging the request for bulk load is not as important as
logging the bulk load commit. I do not think of any use for the bulk load
request wal marker.
Do you mind putting an RB for easier review.
I think we would like to use BULK_LOAD for being consistent:
{code}
+ static final byte [] BULK = Bytes.toBytes("HBASE::BULK");
{code}
About jmock it should be ok, but we may want to the escalate the discussion to
dev@ so that other devs are aware.
> Write bulk load events to WAL
> -----------------------------
>
> Key: HBASE-11567
> URL: https://issues.apache.org/jira/browse/HBASE-11567
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Alex Newman
> Attachments: HBASE-11567-v1.patch, HBASE-11567-v2.patch
>
>
> Similar to writing flush (HBASE-11511), compaction(HBASE-2231) to WAL and
> region open/close (HBASE-11512) , we should persist bulk load events to WAL.
> This is especially important for secondary region replicas, since we can use
> this information to pick up primary regions' files from secondary replicas.
> A design doc for secondary replica replication can be found at HBASE-11183.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
