[
https://issues.apache.org/jira/browse/HBASE-7339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536280#comment-13536280
]
Hadoop QA commented on HBASE-7339:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12561761/pre-hbase-7339.v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 85 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3616//console
This message is automatically generated.
> Splitting a hfilelink causes region servers to go down.
> -------------------------------------------------------
>
> Key: HBASE-7339
> URL: https://issues.apache.org/jira/browse/HBASE-7339
> Project: HBase
> Issue Type: Sub-task
> Components: snapshots
> Affects Versions: hbase-6055
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Priority: Blocker
> Fix For: hbase-6055
>
> Attachments: hbase-7339.patch, hbase-7339.v2.patch,
> pre-hbase-7339.patch, pre-hbase-7339.v2.patch
>
>
> Steps:
> - Have a single region table t with 15 hfiles in it.
> - Snapshot it. (was done using online snapshot from HBASE-7321)
> - Clone a snapshot to table t'.
> - t' has its region do a post-open task that attempts to compact region.
> policy does not compact all files. (default seems to be 10)
> - after compaction we have hfile links and real hfiles mixed in the region
> - t' starts splitting
> - creating split references, opening daughers fails
> - hfile links are "split", creating hfile link daughter refs.
> {{<<hfile>\-<region>\-<table>>.<parentregion>}}
> - these "split" hfile links are interpreted as hfile links with table
> {{<table>.<parentregion>}} ->
> {{<<hfile>\-<region>>\-<<table>.<parentregion>>}} (groupings interpreted
> incorrectly)
> - Since this is after the splitting PONR, this aborts the server. It then
> spreads to the next server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
