[ https://issues.apache.org/jira/browse/HBASE-19850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343029#comment-16343029 ]
Toshihiro Suzuki edited comment on HBASE-19850 at 1/29/18 7:56 AM: ------------------------------------------------------------------- I attached the v2 patch. It seems like when RegionReplicas is enabled and a primary region is split, its secondary region will become OFFLINE. So the number of Offline Region will not be zero in this case. I made the test ignored in the RegionReplicas enabled situation. was (Author: brfrn169): I attached the v2 patch. It seems like when RegionReplicas is enabled and a primary region is split, its secondary region will become OFFLINE. So the number of Offline Region will not zero in this case. I made the test ignored in the RegionReplicas enabled situation. > The number of Offline Regions is wrong after restoring a snapshot > ----------------------------------------------------------------- > > Key: HBASE-19850 > URL: https://issues.apache.org/jira/browse/HBASE-19850 > Project: HBase > Issue Type: Bug > Components: snapshots > Reporter: Toshihiro Suzuki > Assignee: Toshihiro Suzuki > Priority: Major > Fix For: 1.5.0 > > Attachments: HBASE-19850-branch-1.patch, > HBASE-19850-v2-branch-1.patch, The number of Offline Regions.png > > > Steps to reproduce are as follows: > 1. Create a table > {code} > create "test", "cf" > {code} > 2. Take a snapshot for the table > {code} > snapshot "test", "snap" > {code} > 3. Load data to the table > {code} > (0...2000).each\{|i| put "test", "row#{i}", "cf:col", "val"} > {code} > 4. Split regions of the table > {code} > split "test" > {code} > 5. Restore the table from the snapshot > > {code} > disable "test" > restore_snapshot "snap" > enable "test" > {code} > > The number of Offline Regions is as follows: > !The number of Offline Regions.png! > The number of Offline Regions should be zero. > It seems like when regions are removed by restoring a snapshot, the number of > Offline Regions becomes wrong. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)