Out of the box, when a user publishes a site multiple times very quickly, the site's nodes can end up multiple times in the queue. This is especially true if the user does this when non of the site's nodes are replicated before.
Is there a way to configure the queue so that when an item that is already in the queue is to be added to queue once again, the queue prevents the second instance to be added (i.e. to behave like a unique queue)?
A solution that might work even better for us is that, pretending that we have a queue with the following elements (head: left, tail: right)
A, B, C, D, E, F, G
And then the user adds, for example, D to it again, the queue deletes the existing D and adds the new D to the end of the queue:
A, B, C, E, F, G, D
Is there a way to configure replication agents/queues to work like this?
Solved! Go to Solution.