[
https://issues.apache.org/jira/browse/HBASE-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594815#comment-16594815
]
Hadoop QA commented on HBASE-20940:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s{color}
| {color:red} HBASE-20940 does not apply to branch-1. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-20940 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12937410/HBASE-20940.branch-1.v5.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/14237/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> HStore.cansplit should not allow split to happen if it has references
> ---------------------------------------------------------------------
>
> Key: HBASE-20940
> URL: https://issues.apache.org/jira/browse/HBASE-20940
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.2
> Reporter: Vishal Khandelwal
> Assignee: Vishal Khandelwal
> Priority: Major
> Fix For: 3.0.0, 1.5.0, 1.3.3, 2.2.0, 2.1.1, 1.4.7, 2.0.3
>
> Attachments: HBASE-20940.branch-1.3.v1.patch,
> HBASE-20940.branch-1.3.v2.patch, HBASE-20940.branch-1.v1.patch,
> HBASE-20940.branch-1.v2.patch, HBASE-20940.branch-1.v3.patch,
> HBASE-20940.branch-1.v5.patch, HBASE-20940.v1.patch, HBASE-20940.v2.patch,
> HBASE-20940.v3.patch, HBASE-20940.v4.patch, result_HBASE-20940.branch-1.v2.log
>
>
> When split happens and immediately another split happens, it may result into
> a split of a region who still has references to its parent. More details
> about scenario can be found here HBASE-20933
> HStore.hasReferences should check from fs.storefile rather than in memory
> objects.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
