[
https://issues.apache.org/jira/browse/HBASE-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093425#comment-14093425
]
Enis Soztutar commented on HBASE-11567:
---------------------------------------
bq. One question I have is, currently I am logging the request by the user for
HBase HFile bulk loading. That being said, does it make sense to have a
different WAL entry when it completes successfully?
Indeed. The whole point of this issue is to add a WAL marker for the COMMIT of
files for bulk load. Since we cannot do an atomic commit of bulk load files in
the FS and also in WAL, we can do the commit in FS first, then write the WAL
entry next, failing the RS if the WAL sync fails.
> 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)
