On Tue, Aug 18, 2009 at 10:07 AM, stephen mulcahy <[email protected]>wrote:
> If you can shutdown hbase, then 3., is for sure the way to go -- its >> complete and runs quickest. I'm surprised though that it would complain >> of >> missing blocks when fsck does not. >> > > Yeah, I was too. I figured a clean bill of health from fsck was good enough > - but it looks like it missed something. Does it seem likely my hbase is > somehow corrupt or is it robust enough to tolerate those missing blocks? > Running a count on my old and new hbase - it looks like my new hbase (from > the backup) has slightly less rows ... but is much much faster. > > Is there a hbase fsck or verification process? We are working on it (HBASE-7). Meantime, try the rowcounter MR program. It reads all rows in your table. If a problem, it'll fail: ./bin/hadoop jar hbase-X.X.X.jar rowcounter > > > Can we get you to migrate to 0.20.0? >> > > I plan to. But I wasn't clear it was safe to yet - is it? :) > Its as safe -- safer -- than 0.19.x. Let us know if you need a bit of help with migration. St.Ack
