You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2018/02/20 23:33:32 UTC
[GitHub] rdhabalia opened a new pull request #1262: Broker should not start replicator for root partitioned-topic
rdhabalia opened a new pull request #1262: Broker should not start replicator for root partitioned-topic
URL: https://github.com/apache/incubator-pulsar/pull/1262
### Motivation
Recently, multiple times we have seen that for a specific topic, all repl clusters reached to backlog quota in below scenario.
1. Initially client had non-partitioned topic in one of the colo (eg: topic1) and then client had made it partitioned-topic with partition 2.
2. Now when broker tires to load bundle it tries to load non-partition topic (topic1) which starts replication-producer which internally creates producer on partitioned-topic (topic1-partition-1 and topic1-partition-2) because topic has been converted to partitioned-topic in global-zk.
3. Now, when broker tries to load actual partition topic: topic1-partition-1 at that time replication producer fails to connect to remote broker as replicator is already connected.
4. it will cause repl backlog and eventually reached backlog quota.
### Modifications
Broker fails replicator startup for a original topic (eg: topic1) if that topic is configured with partitions.
### Result
Broker will be able to create correct repl-producer and it will not have backlog quota issue.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services