hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14949) Resolve name conflict when splitting if there are duplicated WAL entries
Date Fri, 12 Feb 2016 14:31:18 GMT

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

Duo Zhang updated HBASE-14949:
------------------------------
    Summary: Resolve name conflict when splitting if there are duplicated WAL entries  (was:
Skip duplicate entries when replay WAL.)

> Resolve name conflict when splitting if there are duplicated WAL entries
> ------------------------------------------------------------------------
>
>                 Key: HBASE-14949
>                 URL: https://issues.apache.org/jira/browse/HBASE-14949
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Heng Chen
>         Attachments: HBASE-14949.patch, HBASE-14949_v1.patch, HBASE-14949_v2.patch
>
>
> As HBASE-14004 design,  there will be duplicate entries in different WAL.  It happens
when one hflush failed, we will close old WAL with 'acked hflushed' length,  then open a new
WAL and write the unacked hlushed entries into it.
> So there maybe some overlap between old WAL and new WAL.
> We should skip the duplicate entries when replay.  I think it has no harm to current
logic, maybe we do it first. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message