[
https://issues.apache.org/jira/browse/HBASE-21736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788545#comment-16788545
]
Hudson commented on HBASE-21736:
--------------------------------
Results for branch master
[build #850 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/850/]: (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/master/850//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/master/850//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/master/850//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/master/850//console].
> Remove the server from online servers before scheduling SCP for it in hbck
> --------------------------------------------------------------------------
>
> Key: HBASE-21736
> URL: https://issues.apache.org/jira/browse/HBASE-21736
> Project: HBase
> Issue Type: Bug
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Attachments: HBASE-21736.patch
>
>
> The API is designed for scheduling SCPs for dead servers after we loss all
> the proc wals, but in TestHbck we use hbck to schedule a SCP for a live
> server. In order to pass the test, we need to move it from online servers to
> dead servers otherwise we may retain the assignment on the 'dead' server and
> cause the UT hang. And it is no harm if the server is not online when we call
> this method, so it is fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
