[
https://issues.apache.org/jira/browse/HBASE-21084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594587#comment-16594587
]
Toshihiro Suzuki commented on HBASE-21084:
------------------------------------------
Thank you for reviewing [~Apache9]. Pushing the patches to master and branch-2.
> When cloning a snapshot including a split parent region, the split parent
> region of the cloned table will be online
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-21084
> URL: https://issues.apache.org/jira/browse/HBASE-21084
> Project: HBase
> Issue Type: Bug
> Components: snapshots
> Reporter: Toshihiro Suzuki
> Assignee: Toshihiro Suzuki
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21084.branch-2.001.patch,
> HBASE-21084.branch-2.addendum.001.patch, HBASE-21084.master.001.patch,
> HBASE-21084.master.002.patch, HBASE-21084.master.003.patch,
> HBASE-21084.master.004.patch, HBASE-21084.master.addendum.001.patch
>
>
> Investigating HBASE-21015, I found another issue. It seems like after
> HBASE-20881, the split parent region of the cloned table will be online when
> cloning a snapshot including a split parent region.
> Steps to reproduce are as follows, which is the same as the steps in
> HBASE-21015:
> 1. Create a table
> {code}
> create "test", "cf"
> {code}
> 2. Put some data into the table
> {code}
> (0...2000).each{|i| put "test", "row#{i}", "cf:col", "val"}
> {code}
> 3. Split the table
> {code}
> split "test"
> {code}
> 4. Take a snapshot of the table before CatalogJanitor cleans up the split
> parent region
> {code}
> snapshot "test", "snap"
> {code}
> 5. Clone the snapshot
> {code}
> clone_snapshot "snap", "cloned_table"
> {code}
> After following the above steps, the split parent region of the cloned table
> will be online.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
