Details

    • Sub-task
    • Status: Open
    • Critical
    • Resolution: Unresolved
    • None
    • 3.0.0-alpha-3
    • hbck
    • None

    Description

      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

      Attachments

        1. HBASE-18228.branch-1.3.patch
          50 kB
          Karan Mehta

        Issue Links

          Activity

            People

              Unassigned Unassigned
              larsh Lars Hofhansl
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: