Comment 6 for bug 1263691

Zhengguang,

While RabbitMQ has a TTL extension for messages and queues(http://www.rabbitmq.com/ttl.html), Cinder (and most other projects in OpenStack) doesn't make use of that and that is why there is no consideration of message expiration in Cinder. Therefore, it means the message will stay in the queue for quite very long time, and once scheduler service comes back up, it will consume those messages and makes placement decision for 'create' request eventually.

On the other hand, I'd agree we might take time to think about how to handle message lost, but I think taskflow may have taken care of this already.