Thank you for your replies, guys! Then, I will file this in Apache Jira.
> or better, as per Duo, output a message pointing user to hbck2 operator tools Sure, I will do that. On Sat, Jul 13, 2019 at 12:12 AM Stack <[email protected]> wrote: > +1 on removal in 2.0+ (or better, as per Duo, output a message pointing > user to hbck2 operator tools). Yes, OMR destroys the hbase2 meta table. It > is in violation of our attempt at having hbck1 tooling be read-only in > hbase2. > > Thanks for bringing this up Toshihiro, > S > > On Wed, Jul 10, 2019 at 8:47 PM Toshihiro Suzuki <[email protected]> > wrote: > > > Hi folks! > > > > I think we no longer support OfflineMetaRepair in HBase-2.x and it has a > > critical bug that breaks the meta data: > > https://issues.apache.org/jira/browse/HBASE-21665 > > > > Actually, I have seen several cases where some users ran > OfflineMetaRepair > > mistakenly in their cluster and corrupted their meta data. > > > > Also, new meta rebuilding tool is being developed by Wellington at the > > moment in HBCK2: > > https://issues.apache.org/jira/browse/HBASE-22567 > > > > So I think we can remove OfflineMetaRepair in the master branch and > > branch-2+. What do you think? > > > > If no objections, I'll file this in Apache Jira. > > > > Regards, > > Toshi > > >
