You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Karan Mehta (JIRA)" <ji...@apache.org> on 2018/03/07 18:43:00 UTC
[jira] [Commented] (HBASE-18228) HBCK improvements
[ https://issues.apache.org/jira/browse/HBASE-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389950#comment-16389950 ]
Karan Mehta commented on HBASE-18228:
-------------------------------------
[~lhofhansl] A patch was attempted for this JIRA. However it doesn't seem as useful as expected. Would you mind to discuss other potential improvements here?
FYI, this issue is specifically addressing branch-1.3 (possibly 1.4).
> 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.5.0, 1.4.3
>
> 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
(v7.6.3#76005)