[
https://issues.apache.org/jira/browse/HBASE-23590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006520#comment-17006520
]
Hudson commented on HBASE-23590:
--------------------------------
Results for branch branch-2
[build #2403 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2403/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2403//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/2403//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/2403//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Update maxStoreFileRefCount to maxCompactedStoreFileRefCount
> ------------------------------------------------------------
>
> Key: HBASE-23590
> URL: https://issues.apache.org/jira/browse/HBASE-23590
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.3.0, 1.6.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 1.6.0
>
>
> As per discussion on HBASE-23349, RegionsRecoveryChore should use max
> refCount on compacted away store files and not on new store files to
> determine when to reopen the region. Although work on HBASE-23349 is in
> progress, we need to at least update the metric to get the desired refCount
> i.e. max refCount among all compacted away store files for a given region.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
