[
https://issues.apache.org/jira/browse/HBASE-23322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979804#comment-16979804
]
Hudson commented on HBASE-23322:
--------------------------------
Results for branch branch-2
[build #2361 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2361/]:
(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/2361//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/2361//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/2361//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> [hbck2] Simplification on HBCKSCP scheduling
> --------------------------------------------
>
> Key: HBASE-23322
> URL: https://issues.apache.org/jira/browse/HBASE-23322
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.2.3
>
> Attachments:
> 0001-HBASE-23322-hbck2-Simplification-on-HBCKSCP-scheduli.patch
>
>
> I can make the scheduling of HBCKSCP simpler. I can also fix a bug in parent
> issue that I notice after exercising it a bunch on a cluster.
> The bug is that 'Unknown Servers' seem to be retained in the Map of reporting
> servers. They are usually cleared just before an SCP is scheduled but
> scheduling HBCKSCP doesn't go the usual route.
> The patch here forces HBCKSCP via the usual SCP route only at the scheduling
> time, context dictates whether SCP or the scouring HBCKSCP.
> Let me put up a patch and will test in meantime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
