[
https://issues.apache.org/jira/browse/HBASE-21192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619791#comment-16619791
]
stack commented on HBASE-21192:
-------------------------------
h2. STUCK Region Redux
The hbck2 tool can now do bulk assigning (HBASE-21156). On a cluster with 60k
regions stuck in the OPENING state (no locks held -- the OPENING state came
about because all MasterProcWALs had been removed from under a running
cluster), I did the following:
{code}
# First get list of all the STUCK and OPENING regions
$ grep STUCK master.log|grep OPENING|sed -e "s/^.*region=//"|sort -u >
/tmp/stuck.txt
# Split the file with 60k STUCK regions into files of 1k regions each.
$ split -l 1000 /tmp/stuck.txt STUCK
# Feed each file to the hbck2 tool... call assigns and pass list of 1k encoded
region names.
$ for i in `ls STUCK*`; do ls $i;
HBASE_CLASSPATH_PREFIX=./hbase-hbck2-1.0.0-SNAPSHOT.jar hbase
org.apache.hbase.HBCK2 assigns `cat $i|tr "\n" " "`; done
{code}
> Add HOW-TO repair damaged AMv2.
> -------------------------------
>
> Key: HBASE-21192
> URL: https://issues.apache.org/jira/browse/HBASE-21192
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: stack
> Assignee: stack
> Priority: Major
>
> Need a page or two on how to do various fixups. Will include doc on how to
> identify particular circumstance, how to run a repair, as well as caveats
> (e.g. if no log recovery, then region may be missing edits).
> Add pointer to log messages, especially those that explicitly ask for
> operator intervention; e.g. Master#inMeta.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
