[
https://issues.apache.org/jira/browse/HBASE-24069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120840#comment-17120840
]
Hudson commented on HBASE-24069:
--------------------------------
Results for branch branch-1
[build #1305 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1305/]:
(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-1/1305//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1305//JDK7_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-1/1305//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> Extend HBASE-16209 strategy (Provide an ExponentialBackOffPolicy sleep
> between failed region open requests) to region close and split requests
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-24069
> URL: https://issues.apache.org/jira/browse/HBASE-24069
> Project: HBase
> Issue Type: Improvement
> Components: Region Assignment
> Affects Versions: 1.6.0
> Reporter: Andrew Kyle Purtell
> Assignee: Sandeep Guggilam
> Priority: Major
> Fix For: 3.0.0-alpha-1, 1.7.0, 2.4.0
>
> Attachments: HBASE-24069.branch-1.001.patch
>
>
> In HBASE-16209 we provide an ExponentialBackOffPolicy sleep between failed
> region open requests. This should be extended to also apply to region close
> and split requests. Will reduce the likelihood of FAILED_CLOSE transitions in
> production by being more tolerant of temporary regionserver loading issues,
> e.g. CallQueueTooBigException.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)