As per Sean, bypass with optional 'force' (override) and recurse for case where a procedure had spawned children was the mechanism Allan implemented after a chat about merits of procedure delete. I found it of use doing fixup to clusters I'd intentionally damaged testing candidates. Procedures are usually part of a fabric with relations that an operator might have trouble unraveling. It was thought that the bypass would be safer than a delete, likely to cause more damage than solution.
Interested in the issues you are seeing on Master branch Sergey. Thanks, S On Fri, Jan 25, 2019 at 1:54 PM Sean Busbey <bus...@apache.org> wrote: > that's already present, see the README for the "bypass" command: > > https://github.com/apache/hbase-operator-tools/tree/master/hbase-hbck2 > > On Fri, Jan 25, 2019 at 3:40 PM Sergey Shelukhin > <sergey.sheluk...@microsoft.com.invalid> wrote: > > > > I think one thing that is needed for HBCK2 for AMv2 is to be able to > delete single procedures from store. > > We are evaluating master (whose assignment is very similar to branch-2) > right now and I have to delete proc WAL pretty much every day because some > procedure(s) are in bad state, but deleting the entire WAL also causes > other issues. > > It should be possible to remove some offending procedure while master is > offline and/or online. > > > > -----Original Message----- > > From: 张铎(Duo Zhang) <palomino...@gmail.com> > > Sent: Friday, January 18, 2019 5:52 PM > > To: HBase Dev List <dev@hbase.apache.org> > > Subject: Re: [DISCUSS] Moving towards a branch-2 line that can get the > 'stable' pointer. > > > > OK, the original issue is HBCK2 for AMv2, but here we need to do more, > not only for AMv2. > > > > Let me open a new issue and post what Andrew said above there. > > >
