[
https://issues.apache.org/jira/browse/HBASE-21372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662908#comment-16662908
]
Hudson commented on HBASE-21372:
--------------------------------
Results for branch branch-2.0
[build #1009 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1009/]:
(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.0/1009//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.0/1009//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1009//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Set hbase.assignment.maximum.attempts to Long.MAX
> -------------------------------------------------
>
> Key: HBASE-21372
> URL: https://issues.apache.org/jira/browse/HBASE-21372
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21372.branch-2.1.001.patch,
> HBASE-21372.branch-2.1.001.patch
>
>
> From parent issue, [~allan163] suggests that we not give up on assign unless
> there a change -- an SCP triggers failure -- or at the extreme, an operator
> intervenes. This jibes w/ how we're thinking about assign (or to put it
> another way, we have no handling for the case where we exhaust retries).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
