[
https://issues.apache.org/jira/browse/HBASE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923243#action_12923243
]
Jonathan Gray commented on HBASE-2819:
--------------------------------------
I spent some time putting this onto trunk. The repair stuff that we added to
work on the old master doesn't make much sense anymore on the new master. For
example, it should be impossible for a region to just go unassigned with no
trace of how it happened. If it doesn't open properly there is a ZK node.
This is not to say we don't need hbck with the new master. I just don't think
we know what issues we'll run into, but they'll certainly be different. I
could imagine having RIT nodes stuck in weird states and things like that.
Should I put up a patch with what I have against trunk? It has some basic
versions of the same repair stuff that worked on the old master, but like I
said, may not make much sense.
And then we can open a new jira for 0.92 to make hbck even gooder?
> hbck should have the ability to repair basic problems
> -----------------------------------------------------
>
> Key: HBASE-2819
> URL: https://issues.apache.org/jira/browse/HBASE-2819
> Project: HBase
> Issue Type: New Feature
> Components: scripts
> Reporter: Todd Lipcon
> Assignee: Alexander Georgiev
> Priority: Critical
> Fix For: 0.90.0
>
> Attachments: HBASE-2819.patch
>
>
> Right now, the hbck utility can detect issues with region deployment but
> can't fix them.
> It should be able to handle basic things like closing one side of a double
> assignment, re-adding something to META, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
