[
https://issues.apache.org/jira/browse/HBASE-22632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874529#comment-16874529
]
Hudson commented on HBASE-22632:
--------------------------------
Results for branch branch-2
[build #2031 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2031/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2031//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2031//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2031//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> SplitTableRegionProcedure and MergeTableRegionsProcedure should skip store
> files for unknown column families
> ------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22632
> URL: https://issues.apache.org/jira/browse/HBASE-22632
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Attachments: HBASE-22632-UT.patch
>
>
> Hit this problem in our internal staging cluster. Not sure why, but probably,
> there was a partial successful 'alter table' call that removed a family. As
> it is 'partial successful', there are still some stale store files of the
> removed family left under the region directory. And in
> SplitTableRegionProcedure and MergeTableRegionsProcedure, we will get all the
> store files by listing the file system, so we will also get the stale store
> files for the family which should have been removed already, and then causes
> NPE when we want to access the ColumnFamilyDescriptor.
> Although it is not the common case that there are store files for removed
> families, but FWIW, I think we can do something to make our procedures more
> robust...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
