Found this problem when implementing HBASE-28199. The reason why the code change in HBASE-28199 can expose the problem is that, we add the crash code between adding the procedure to root procedure state and updating store, so we can reproduce the problem that later procedure can be persistent earlier reliably, and then cause trouble while loading procedure.
It is not very easy to reproduce in the normal world but if it happens, it will be a very big problem and can only be recovered manually. I think this is a critical problem which we should fix ASAP. Thanks.
