[ 
https://issues.apache.org/jira/browse/HBASE-20087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated HBASE-20087:
-----------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s:     (was: 1.4.3)
     Release Note: The AssignmentManager will attempt to assign regions in 
FAILED_OPEN state at an interval specified by the configuration setting 
"hbase.assignment.failed.open.retry.period", defaulting to 300000 (5 minutes). 
If a transient condition leads a region to repeatedly fail to open sufficient 
to transition into FAILED_OPEN state, such as the temporary inability to 
satisfy a RSGroups assignment constraint after server failures, the retries may 
automatically redeploy the region without operator intervention. Set to 0 to 
disable and keep the old behavior where regions in FAILED_OPEN state are left 
to operators to manually reassign. 
           Status: Resolved  (was: Patch Available)

Pushed to branch-1.

If we want something similar like this in AMv2 I could do a forward port. 

> Periodically attempt redeploy of regions in FAILED_OPEN state
> -------------------------------------------------------------
>
>                 Key: HBASE-20087
>                 URL: https://issues.apache.org/jira/browse/HBASE-20087
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, Region Assignment
>    Affects Versions: 1.4.2
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Major
>             Fix For: 1.5.0
>
>         Attachments: 
> 0001-W-4723090-Port-the-RIT-FAILED_OPEN-state-hack-from-R.patch, 
> HBASE-20087-branch-1.patch, HBASE-20087-branch-1.patch
>
>
> Because RSGroups can cause permanent RIT with regions in FAILED_OPEN state, 
> we added logic to the master portion of the RSGroups extention to enumerate 
> RITs and retry assignment of regions in FAILED_OPEN state.
> However, this strategy can be applied generally to reduce need of operator 
> involvement in cluster operations. Now an operator has to manually resolve 
> FAILED_OPEN assignments but there is little risk in automatically retrying 
> them after a while. If the reason the assignment failed has not cleared, the 
> assignment will just fail again. Should the reason the assignment failed be 
> resolved, then operators don't have to do more in order for the cluster to 
> fully heal. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to