Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
What is expected behavior when combining 100GB retention policy, 1GB backlog quota and a consumer with SubscriptionInitialPosition.Earliest setting?
See original GitHub issueI couldn’t get clear understanding of pulsar behavior from documentation in the following situation.
Supposing a namespace configured 100GB retention policy, 1GB backlog quotas and 100GB messages are pushed with no subscription, what will happen if a subscription with SubscriptionInitialPosition.Earliest setting is created?
Is the backlog of the newly created subscription over 1GB backlog quotas?
Will a producer immediately stop because of producer_request_hold policy?
I originally discussed about this question on slack and was recommended to rise issue in order to get clarification. https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1594348193122700
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@sijie Thank you for your answer. That is to say, in order for lately created subscription to read all retained messages without interfering a producer, should backlog quota be set to the same size as retention policy? (In this case, 100GB.) If so, as retention policy is applied to the messages only not in backlog, do I need to estimate the maximum size of disk space at twice the size of the retention policy?
I see. I’m also interested in how retention policy and backlog quotas affect compactioned topic. I think there is not much information on this.