[
https://issues.apache.org/jira/browse/HBASE-16209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399748#comment-15399748
]
Matteo Bertozzi commented on HBASE-16209:
-----------------------------------------
sorry, late for the review.. but why are we doing another lookup for the region
state? we are already looping on the region state... so the new "state" that we
are looking up should be the same to the "rs" we are looping on, no?
{code}
<%for RegionState rs : rit %>
+ String name = rs.getRegion().getEncodedName();
+ RegionState state = assignmentManager.getState(name);
+ AtomicInteger numOpenRetries =
failedRegionTracker.get(name);
{code}
> Provide an ExponentialBackOffPolicy sleep between failed region open requests
> -----------------------------------------------------------------------------
>
> Key: HBASE-16209
> URL: https://issues.apache.org/jira/browse/HBASE-16209
> Project: HBase
> Issue Type: Bug
> Reporter: Joseph
> Assignee: Joseph
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-16209-branch-1.patch, HBASE-16209-v2.patch,
> HBASE-16209.patch
>
>
> Related to HBASE-16138. As of now we currently have no pause between retrying
> failed region open requests. And with a low maximumAttempt default, we can
> quickly use up all our regionOpen retries if the server is in a bad state. I
> added in a ExponentialBackOffPolicy so that we spread out the timing of our
> open region retries in AssignmentManager. Review board at
> https://reviews.apache.org/r/50011/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
