I notice this issue while running IntegrationTestDDLMasterFailover, it can be simply reproduced by executing this on active master (tested on two masters + 3rs cluster setup)
Logs show that new active master is trying to locate hbase:meta table on restarted active master
and because of above master is unable to read hbase:meta table:
which cause master is unable to complete start.
I have also notices that in this case value of /hbase/meta-region-server znode is always pointing on restarted active master (hnode1 in my cluster ).
I was able to workaround this issue by repeating same scenario with following:
So issue is probably caused by staled value in /hbase/meta-region-server znode. I will try to create patch based on above.