In the deploy/request messages sent from TC, we need to add a message TTL, for example, 5 minutes, so they expire – i.e., the requests are discarded – after the time window. Otherwise, if the elasticity module is down for some time, when it starts up, it will process the requests that were sent long time ago and perform that action, which may be undesired.

This needs to happen in Tools Catalog when creating the msg to send to the RabbitMQ deploy request queue.

This occurred on May 12, 2016. The elasticity module seemed to have stopped for 8 hours on bd-elasticity. Upon restarting, it picked up a stop request from the deployment queue, and stopped the OCR extrators for dts-dev. So the bi-hourly tests failed.