Testing tip of branch-2.0, ran into this:
It then shows as the below in the UI:
This is what we'd just read from hbase:meta:
Before this, we'd just logged this:
2018-07-29 01:33:39,786 INFO [PEWorker-14] assignment.RegionStateStore: pid=1823 updating hbase:meta row=533fb79ba23b27e9e0715b51daeb30c1, regionState=CLOSED
Going back in history, we do the above each time the Master gets restarted so the region is offlined and never brought back online.
It is failing here:
Its the parent move region that is trying to run and failing. It is not RUNNABLE? Because the subprocedure was 'done' but not fully?