[
https://issues.apache.org/jira/browse/HBASE-18370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086182#comment-16086182
]
Gary Helmling commented on HBASE-18370:
---------------------------------------
One of the problems we have with the region assignment retries in 1.3 and prior
is the lack of backoff between retry attempts, so we burn through the retries
quickly. With HBASE-16209 in branch-1+, we now have a backoff policy for
region open attempts. If we just change the default configuration for max
retries to Integer.MAX_VALUE, this should effectively give us "retry forever"
for region open, which seems much better than the current behavior.
So I'm not sure we need anything more than a config change. Are there any
places where this will not be sufficient? I'm not sure offhand if we would
give up on master failover?
> Master should attempt reassignment of regions in FAILED_OPEN state
> ------------------------------------------------------------------
>
> Key: HBASE-18370
> URL: https://issues.apache.org/jira/browse/HBASE-18370
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
>
> Currently once a region goes into FAILED_OPEN state this requires operator
> intervention. With some underlying causes, this is necessary. With others,
> the master could eventually successfully deploy the region without humans in
> the loop. The master should optionally attempt automatic resolution of
> FAILED_OPEN states with a strategy of: delay, unassign, reassign.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
