This message was deleted.
# general
s
This message was deleted.
m
after failover, are you seeing the consumer processing the messages at the same rate on cluster 1?
s
Message rate in cluster 1 falldown to zero after failover
m
since backlog of replication backlog is increasing, I doubt if replication is working fine.
if you are using replicated subscription, I hope this was enabled
enableReplicatedSubscriptions=true
Can you disable replicated subscription and validate if geo replication is working as expected. Perhaps some bug with the replciated subscription.
s
Yes Replication is working fine but storage was incresing over the time in the remote cluster(we enabled enableReplicatedSubscriptions=true both on broker and client) But by disabling the subscriptionReplication on client, we have observed that the offset was not maintaining and the consumer was not restarted from the failure point. We are looking for the offset to be maintained with atleastOnce semantics during DR. Thanks
r
Did you check if the replication backlog is increasing for all the topics/partitions or for some particular partition? We have seen a similar issue earlier when there were some missing partitions for the topics in the remote cluster.
s
We are not actively producing and consuming on other topics. We are using this topic t1 for DR activity and we are continually producing and consuming from the other clusters within the instance during DR