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-15441) Fix WAL splitting when region has moved multiple times
Date Thu, 17 Mar 2016 08:10:33 GMT

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

Hudson commented on HBASE-15441:
--------------------------------

ABORTED: Integrated in HBase-1.3 #606 (See [https://builds.apache.org/job/HBase-1.3/606/])
HBASE-15441 Fix WAL splitting when region has moved multiple times (eclark: rev dd4ac94387bd64623fcf484cef1c99ff13a9e29e)
* hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/RegionReplicaReplicationEndpoint.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALSplitter.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALEdit.java


> Fix WAL splitting when region has moved multiple times
> ------------------------------------------------------
>
>                 Key: HBASE-15441
>                 URL: https://issues.apache.org/jira/browse/HBASE-15441
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.0, 1.2.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Blocker
>             Fix For: 2.0.0, 1.3.0, 1.2.1, 1.4.0
>
>         Attachments: HBASE-15441-v1.patch, HBASE-15441-v2.patch, HBASE-15441-v3.patch,
HBASE-15441-v4.patch, HBASE-15441-v5.patch, HBASE-15441.patch
>
>
> Currently WAL splitting is broken when a region has been opened multiple times in recent
minutes.
> Region open and region close write event markers to the wal. These markers should have
the sequence id in them. However it is currently getting 1. That means that if a region has
moved multiple times in the last few mins then multiple split log workers will try and create
the recovered edits file for sequence id 1. One of the workers will fail and on failing they
will delete the recovered edits. Causing all split wal attempts to fail.
> We need to:
> # make sure that close get the correct sequence id for open.
> # Filter all region events from recovered edits
> It appears that the close event with a sequence id of one is coming from region warm
up.



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

Mime
View raw message