Story #8084
Story #8061: develop queue-based processing system for the CN
determine the backup strategy for rabbitMQ
Start date:
2017-04-26
Due date:
% Done:
0%
Story Points:
Sprint:
Description
Do we need to back up not only the rabbitMQ configuration, but also messages? Consider that we might have long-lived dead-letter or task failed queues...
History
#1 Updated by Rob Nahf over 7 years ago
#2 Updated by Dave Vieglais over 7 years ago
The rabbitmq queues should be replicated across machines, so failure of one or two machines could be restored from the remaining. This is the case with much of the CN infrastructure.
Second, the information contained in the queues could be restored by reindexing content that has been added or modified since time before the failure.
Hence it seems that it should be sufficient to ensure that the rabbitmq configuration is preserved to enable the instances to be reinstalled as necessary.
#3 Updated by Dave Vieglais almost 7 years ago
- Sprint set to Infrastructure backlog
