[
https://issues.apache.org/jira/browse/HBASE-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052788#comment-16052788
]
Jonathan Hsieh commented on HBASE-18228:
----------------------------------------
The problem in 2.x is that some of the repairs (especially around assignment)
are likely no longer valid because they use operations that subsumed by the new
assignment manager, and new operations for repairs of proc wal may be needed.
> HBCK improvements
> -----------------
>
> Key: HBASE-18228
> URL: https://issues.apache.org/jira/browse/HBASE-18228
> Project: HBase
> Issue Type: Improvement
> Components: hbck
> Reporter: Lars Hofhansl
> Priority: Critical
> Fix For: 1.4.0
>
>
> 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)
