hbase-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/HBASE-14949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152249#comment-15152249
] 

Hudson commented on HBASE-14949:
--------------------------------

FAILURE: Integrated in HBase-1.3 #559 (See [https://builds.apache.org/job/HBase-1.3/559/])
HBASE-14949 Resolve name conflict when splitting if there are duplicated (zhangduo: rev b8f92312b3e683c0181c4baac088f520cf7d0656)
* hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestWALReplay.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALSplitter.java


> 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-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)

Mime
View raw message