[
https://issues.apache.org/jira/browse/HBASE-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karan Mehta updated HBASE-18228:
--------------------------------
Attachment: HBASE-18228.branch-1.3.patch
Patch includes the changes:
New switches for hbck
* {{-dryRun}} --> Runs HBCK without affecting anything. Also prints out what
potential changes will this particular run make. It cannot output full detail
since some operations can only be performed after the first one is done.
* {{-i}} --> Interactive HBCK. Asks for user input before every potential
modification. For example, before fixing a particular hole in META, creating a
new .regionInfo file etc.
Also asks user confirmation for options such as -repair and -repairHoles which
internally run several other switches.
[~apurtell] [~jmhsieh] [~mdrob] Please review.
> HBCK improvements
> -----------------
>
> Key: HBASE-18228
> URL: https://issues.apache.org/jira/browse/HBASE-18228
> Project: HBase
> Issue Type: Improvement
> Components: hbck
> Reporter: Lars Hofhansl
> Assignee: Karan Mehta
> Priority: Critical
> Fix For: 1.4.0
>
> Attachments: HBASE-18228.branch-1.3.patch
>
>
> We just had a prod issue and running HBCK the way we did actually causes more
> problems.
> In part HBCK did stuff we did not expect, in part we had little visibility
> into what HBCK was doing, and in part the logging was confusing.
> I'm proposing 2 improvements:
> 1. A dry-run mode. Run, and just list what would have been done.
> 2. An interactive mode. Run, and for each action request Y/N user input. So
> that a user can opt-out of stuff.
> [~jmhsieh], FYI
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
