You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/03/02 02:52:00 UTC
[jira] [Updated] (HBASE-17319) Truncate table with preserve after
split may cause truncation to fail
[ https://issues.apache.org/jira/browse/HBASE-17319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-17319:
--------------------------
Fix Version/s: (was: 1.4.0)
(was: 2.0.0)
> Truncate table with preserve after split may cause truncation to fail
> ---------------------------------------------------------------------
>
> Key: HBASE-17319
> URL: https://issues.apache.org/jira/browse/HBASE-17319
> Project: HBase
> Issue Type: Bug
> Components: Admin
> Affects Versions: 1.1.7, 1.2.4
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Major
> Attachments: 17319-branch-1.patch, 17319.stack, HBASE-17319-branch-1.patch, HBASE-17319-branch-1.patch, HBASE-17319.patch, TestTruncateTableProcedure-output.tar.gz
>
>
> In truncateTableProcedue , when getting tables regions from meta to recreate new regions, split parents are not excluded, so the new regions can end up with the same start key, and the same region dir:
> {noformat}
> 2016-12-14 20:15:22,231 WARN [RegionOpenAndInitThread-writetest-1] regionserver.HRegionFileSystem: Trying to create a region that already exists on disk: hdfs://hbasedev1/zhengyan-hbase11-func2/.tmp/data/default/writetest/9b2c8d1539cd92661703ceb8a4d518a1
> {noformat}
> The truncateTableProcedue will retry forever and never get success.
> A attached unit test shows everything.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)