hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-11511) Write flush events to WAL
Date Mon, 14 Jul 2014 18:36:05 GMT

     [ https://issues.apache.org/jira/browse/HBASE-11511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Enis Soztutar updated HBASE-11511:
----------------------------------

    Attachment: hbase-11511_v1.patch

Here is a patch that writes START_FLUSH, COMMIT_FLUSH and ABORT_FLUSH events to WAL.  

I tried to take special care to the exception code paths to make sure that we do not cause
hangs, etc on flush fail and region close. 

COMMIT_FLUSH is written after the store files are actually committed, and it does not happen
atomically ( of course). This means that we can miss COMMIT_FLUSH events after START_FLUSH
if the region server fails, etc. Corresponding HBASE-11512 might help with WAL tailers to
pick up new files if we persist all the hfiles for the region at region open time to WAL.


I am running the unit tests.

> Write flush events to WAL
> -------------------------
>
>                 Key: HBASE-11511
>                 URL: https://issues.apache.org/jira/browse/HBASE-11511
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>         Attachments: hbase-11511_v1.patch, hbase-11511_v1.patch
>
>
> We used to write COMPLETE_FLUSH event to WAL until it got removed in 0.96 in issue HBASE-7329.

> For secondary region replicas, it is important to share the data files with the primary
region. So we should reintroduce the flush wal markers so that the secondary region replicas
can pick up the newly flushed files from the WAL and start serving data from those. 
> A design doc which explains the context a bit better can be found in HBASE-11183. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message