-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retention 0mb and BacklogQuota 0mb #154
Comments
@merlimat what do you think of this? there's now way right now to set an unlimited size retention or backlog quota. |
Sorry @sschepens, I missed this issue back in the days. I just created #1135 and I'll create another PR to clarify in the documentation |
Added 2nd PR for docs changes: #1141 |
Thanks for taking the time! |
* fix producer handler memory leak * consumer removed from client handler when closed * golanglint * add tests & fix deadlock when handler close * make handlers delete in closeOnce to prevent unnecessary calls * goimports
In Pulsar standalone mode, If advertisedAddress not set, it is hard coded as "localhost": ``` if (this.getAdvertisedAddress() != null) { // Use advertised address from command line config.setAdvertisedAddress(this.getAdvertisedAddress()); zkServers = this.getAdvertisedAddress(); } else if (isBlank(config.getAdvertisedAddress())) { // Use advertised address as local hostname config.setAdvertisedAddress("localhost"); } else { // Use advertised address from config file } ``` And in KoP, if host address not set in listeners, it will use advertised address to do the config. Then the value read from conf.properties is outdated. This PR update it with right value.
apache#154) * [fix][monitor] Fix reporting pulsar_subscription_blocked_on_unacked_messages metric (apache#18621) * Update the NamespaceStatsAggregatorTest to use SimpleTextOutputStream instead of PrometheusMetricStreams
It's not documented what setting a retention of 0mb actually does, neither with BacklogQuota.
By the way, both of this should actually mean no limit to be consistent with other settings.
If i'm not mistaken, setting those to 0mb will make brokers delete all data when they check.
In our case we want a retention based on time and not on size, so we actually want unlimited retention, and probably backlog quota too.
The text was updated successfully, but these errors were encountered: