You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "lhotari (via GitHub)" <gi...@apache.org> on 2025/01/02 07:16:31 UTC
Re: [I] [Enhancement] Support replicating already replicated messages and multi-hop forwarding replication topologies [pulsar]
lhotari commented on issue #23771:
URL: https://github.com/apache/pulsar/issues/23771#issuecomment-2567362696
> This idea sounds very suitable for message replication, but we have a subscription replication feature. When using a star topology, subscription replication will be complex. I remember that subscribing to replication depends on the order of messages. What do you think?
@nodece For subscription replication, it might not make sense to handle subscription replication in a star topology. The reason for this is that I cannot think of a use case where this would make sense. What would even be the expected behavior in that case?
Even in the current subscription replication, it is not supported to have active consumers in different clusters for the same subscription. There won't be errors if there are active consumers on both clusters, but the messages will get randomly delivered to either consumers or both consumers.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org