On Mon, Dec 10, 2018 at 11:32 AM Stack <[email protected]> wrote: > > On Thu, Dec 6, 2018 at 7:45 AM Sean Busbey <[email protected]> wrote: > > > ... > > > Once I confirmed the given RS was not currently doing anything for any > > of those regions I figured I'd use HBCK2 to run an assigns to get > > things fixed. However, since there were like 900 RITs, the Master UI > > was unusable for getting a complete list. > > > > How unusable Sean? Was it up? >
It was up. but we paginate the results so there's only 5 at a time. I'm not going to click through ~200 pages to get the list of things to copy/paste. > > > Also with that many all in > > the same state I want to be able to automate running against each of > > them. > > > > I ended up greping the master log file and pulling out the WARN > > messages about RIT to tease out the list of regions, then passed those > > to hbck2. > > > > > > Yeah. You saw the doc over on hbck2? > https://github.com/apache/hbase-operator-tools/tree/master/hbase-hbck2 > indeed. super helpful and why I knew how to use the assigns to bypass things. > Did you have: > > commit fa6373660f622e7520a9f2639485cc386f18ede0 > Author: jingyuntian <[email protected]> > Date: Thu Nov 8 15:30:30 2018 +0800 > > HBASE-21410 A helper page that help find all problematic regions and > procedures > > It dumps the problematic on the UI so can save on messing in logs. > Hurm. the fix version on HBASE-21410 suggest I should have had it, but I don't think that page is present? I must be missing something. Between that and HBASE-21283 I should have plenty to put into a troubleshooting blurb. :)
