[jira] [Issue Comment Deleted] (HBASE-17319) Truncate table with preserve after split may cause truncation to fail

["Allan Yang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-17319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allan Yang updated HBASE-17319:
-------------------------------
    Comment: was deleted

(was: The TestTruncateTableProcedure passed on my environment, I can't reproduce the exceptions in master branch, maybe a glitch for Hudson, how can I trigger a Hudson rerun?)

> 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
>             Fix For: 1.4.0
>
>         Attachments: HBASE-17319-branch-1.patch, HBASE-17319.patch
>
>
> 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
(v6.3.4#6332)