+1 Earlier this came up as a need for cancelling individual procedures. The capability to cancel a procedure was removed from the procedure framework because it is hard to do reliably in all cases. It should at least be possible to cancel and remove procedures that have not executed yet but are in queue / are stuck. Otherwise one has to resort to removing the proc WAL to drain the queue, losing needed work as well as the troublesome entries. It could also be reasonable to allow abort requests, which might be rejected depending on implementation, and then allow abort requests in some limited cases (hopefully, an increasing number over time).
On Fri, Jan 25, 2019 at 1: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. > > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
