[
https://issues.apache.org/jira/browse/HBASE-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436360#comment-16436360
]
Umesh Agashe commented on HBASE-18792:
--------------------------------------
bq. As someone who has relied on some of these fix options in the past
(especially fixAssigments and fixMeta), what should an operator do instead if a
table gets into a bad state?
HBase 2.0 includes AMv2 which handles assignments through procedures that are
persisted in meta. With every restart of Master, procedures are re-tried from
the last persisted state/ step. Whatever is in meta takes precedence over view
that region servers have or HDFS. Same applies for .regioninfo and .tableinfo
files. HBase 2.0 doesn't use those files. So options like: -fixAssignments,
-fixHdfsOrphans, -fixTableOrphans are not required. Submitting/ re-submitting
procedures (operations) can sometimes replace -fixMeta.
> hbase-2 needs to defend against hbck operations
> -----------------------------------------------
>
> Key: HBASE-18792
> URL: https://issues.apache.org/jira/browse/HBASE-18792
> Project: HBase
> Issue Type: Task
> Components: hbck
> Reporter: stack
> Assignee: Umesh Agashe
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: hbase-18792.master.001.patch
>
>
> hbck needs updating to run against hbase2. Meantime, if an hbck from hbase1
> is run against hbck2, it may do damage. hbase2 should defend itself against
> hbck1 ops.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
