[
https://issues.apache.org/jira/browse/HBASE-16209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402371#comment-15402371
]
Joseph commented on HBASE-16209:
--------------------------------
Oh thanks for catching this [~Apache9]! I found that the bug seemed to be that
I was not checking if the map contained the regionName before getting it and
this was causing a null pointer exception. Altering this code seems to resolve
the Unit Tests. I was just reading through the code and kind of curious why we
do not use the newPlan option for reassigning? And is it ok for me to resubmit
this patch here after making this change?
> 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-addendum.patch,
> HBASE-16209-branch-1-addendum-v2.patch, HBASE-16209-branch-1-addendum.patch,
> 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)
