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

Nihal Jain commented on HBASE-19893:
------------------------------------

Okay sure [~brfrn169]. I think you should add the following UT along with this 
patch. So that the patch verifies that this fix resolves the truncate before 
restore bug.
{code:java}
  @Test 
  public void testRestoreSnapshotAfterTruncate() throws Exception { 
    TableName tableName = 
TableName.valueOf("testRestoreSnapshotAfterTruncate"); 
    SnapshotTestingUtils.createTable(TEST_UTIL, tableName, getNumReplicas(), 
FAMILY); 
    SnapshotTestingUtils.loadData(TEST_UTIL, tableName, 500, FAMILY); 
    int numOfRows = 0; 

    try (Table table = TEST_UTIL.getConnection().getTable(tableName)) { 
      numOfRows = countRows(table); 
    } 
    // take snapshot 
    admin.snapshot("snap", tableName); 
    admin.disableTable(tableName); 
    admin.truncateTable(tableName, false); 
    admin.disableTable(tableName); 
    admin.restoreSnapshot("snap"); 
 
    admin.enableTable(tableName); 
    verifyRowCount(TEST_UTIL, tableName, numOfRows); 
    SnapshotTestingUtils.verifyReplicasCameOnline(tableName, admin, 
getNumReplicas()); 
  } 
{code}

> restore_snapshot is broken in master branch when region splits
> --------------------------------------------------------------
>
>                 Key: HBASE-19893
>                 URL: https://issues.apache.org/jira/browse/HBASE-19893
>             Project: HBase
>          Issue Type: Bug
>          Components: snapshots
>            Reporter: Toshihiro Suzuki
>            Assignee: Toshihiro Suzuki
>            Priority: Critical
>         Attachments: HBASE-19893.master.001.patch, 
> HBASE-19893.master.002.patch, HBASE-19893.master.003.patch, 
> HBASE-19893.master.003.patch
>
>
> When I was investigating HBASE-19850, I found restore_snapshot didn't work in 
> master branch.
>  
> Steps to reproduce are as follows:
> 1. Create a table
> {code:java}
> create "test", "cf"
> {code}
> 2. Load data (2000 rows) to the table
> {code:java}
> (0...2000).each{|i| put "test", "row#{i}", "cf:col", "val"}
> {code}
> 3. Split the table
> {code:java}
> split "test"
> {code}
> 4. Take a snapshot
> {code:java}
> snapshot "test", "snap"
> {code}
> 5. Load more data (2000 rows) to the table and split the table agin
> {code:java}
> (2000...4000).each{|i| put "test", "row#{i}", "cf:col", "val"}
> split "test"
> {code}
> 6. Restore the table from the snapshot 
> {code:java}
> disable "test"
> restore_snapshot "snap"
> enable "test"
> {code}
> 7. Scan the table
> {code:java}
> scan "test"
> {code}
> However, this scan returns only 244 rows (it should return 2000 rows) like 
> the following:
> {code:java}
> hbase(main):038:0> scan "test"
> ROW COLUMN+CELL
>  row78 column=cf:col, timestamp=1517298307049, value=val
> ....
>   row999 column=cf:col, timestamp=1517298307608, value=val
> 244 row(s)
> Took 0.1500 seconds
> {code}
>  
> Also, the restored table should have 2 online regions but it has 3 online 
> regions.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to