Project

General

Profile

Story #8084

Story #8061: develop queue-based processing system for the CN

determine the backup strategy for rabbitMQ

Added by Rob Nahf over 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
d1_indexer
Target version:
-
Start date:
2017-04-26
Due date:
% Done:

0%

Story Points:

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

#2 Updated by Dave Vieglais over 4 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 4 years ago

  • Sprint set to Infrastructure backlog

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)