4d90425031
Earlier when queues had locks, clearQueue() also cleaned up old locks when AbstractProcedureScheduler.clear() was called to reset scheduler for testing failure and recovery. Now with locks decoupled from queues, they need to be separately cleaned up. We can't have clearLocks() as abstract method in AbstractProcedureScheduler because at that level, a procedure scheduler is just a queue. It's only in MasterProcedureScheduler that locks come into picture. So directly overriding clear() method in MPS. Earlier when queues had locks, clearQueue() also cleaned up old locks when AbstractProcedureScheduler.clear() was called. Now with locks decoupled from queues, they need to be separately cleaned up. We can't have clearLocks() as abstract method in AbstractProcedureScheduler because at that level, a procedure scheduler is just a queue. It's only in MasterProcedureScheduler that locks come into picture. So directly overriding clear() method in MPS. Change-Id: If1a0acb418a79f98ce6155541edb0c1e621638e3 |
||
---|---|---|
.. | ||
src | ||
pom.xml |