[jira] [Resolved] (HBASE-14949) Resolve name conflict when splitting if there are duplicated WAL entries

["Duo Zhang (JIRA)" <ji...@apache.org>]

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

Duo Zhang resolved HBASE-14949.
-------------------------------
      Resolution: Fixed
    Release Note: Now we can write duplicated WAL entries into different WAL files. This feature is required by the replication consistency fix and new implementation of WAL writer.

> 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
>          Components: wal
>            Reporter: Heng Chen
>            Assignee: Duo Zhang
>             Fix For: 2.0.0, 1.3.0
>
>         Attachments: HBASE-14949-addendum-branch-1.patch, HBASE-14949-v3.patch, HBASE-14949-v4.patch, HBASE-14949-v5.patch, HBASE-14949.patch, HBASE-14949_v1.patch, HBASE-14949_v2.patch
>
>
> The AsyncFSHLog introduced in HBASE-14790 may write same WAL entries to different WAL files. WAL entry itself is idempotent so replay is not a problem but the intermediate file name and final name when splitting is constructed using the lowest or highest sequence id of the WAL entries written, so it is possible that different WAL files will have same intermediate or final file name when splitting. In the currentm implementation, this will cause split fail or data loss. We need to solve this.



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