-> Active master gets ZK expiry exception.
-> Backup master becomes active.
-> The previous active master retries and becomes the back up master.
Now when the new active master goes down and the current back up master comes up, it goes down again with the zk expiry exception it got in the first step.
In ActiveMasterManager.blockUntilBecomingActiveMaster we try to wait till the back up master becomes active.
When the back up master (it is in back up mode as he got ZK exception), once again tries to come to active we don't get the return value that comes out from
We tend to return the 'cleanSetOfActiveMaster' which was previously false.
Now because of this instead of again becoming active the back up master goes down in the abort() code. Thanks to Gopi,my colleague for reporting this issue.