Hi, does someone have experience with asynchronous geo replication and cluster failures? I have the following scenario: 1. Cluster A with topic X configured to replicate towards Cluster B. 2. Cluster B with topic X configured to replicate towards Cluster A. Now, lets assume that in a failure scenario, Cluster A goes down. Therefore I have clients producing and consuming only from cluster B. As the cluster A is down, the replicator cannot replicate any messages towards it. Therefore, the replication backlog keeps on increasing, while the topic backlog is near 0, as nearly all messages being produced are also consumed. Theoretically , this scenario can pose a challenge, as it can lead to storage being full, because "acknowledged" messages are still waiting to be replicated. I couldn't find any information about these scenarios in the docs, does anyone have any experience with this?

Theoretically , this scenario can pose a challenge, as it can lead to storage being full, because "acknowledged" messages are still waiting to be replicated.

Yes, you need storage to handle this. Pulsar can use S3 as tiered storage, so that's the way how it can handle long durations of downtime, beyond storage available in BookKeeper.

And regarding the TTL, does the replicator use that in anyway to stop replication of expired messages?

And regarding the TTL, does the replicator use that in anyway to stop replication of expired messages?

Expired messages won't get replicated.