You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/10/17 06:24:40 UTC

[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#796afff)

This is an automated email from the ASF dual-hosted git repository.

urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 20dcc0a3058 Docs sync done from apache/pulsar(#796afff)
20dcc0a3058 is described below

commit 20dcc0a305876b7fd9678f14d10355799588fc61
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Mon Oct 17 06:24:34 2022 +0000

    Docs sync done from apache/pulsar(#796afff)
---
 site2/website-next/docs/cookbooks-retention-expiry.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/site2/website-next/docs/cookbooks-retention-expiry.md b/site2/website-next/docs/cookbooks-retention-expiry.md
index 1e552fbd4e2..e50beb0fb39 100644
--- a/site2/website-next/docs/cookbooks-retention-expiry.md
+++ b/site2/website-next/docs/cookbooks-retention-expiry.md
@@ -58,7 +58,7 @@ When a retention limit on a topic is exceeded, the oldest message is marked for
 
 ### Defaults
 
-You can set message retention at instance level with the following two parameters: `defaultRetentionTimeInMinutes` and `defaultRetentionSizeInMB`. Both parameters are set to `0` by default. 
+You can set message retention at instance level with the following two parameters: `defaultRetentionTimeInMinutes` and `defaultRetentionSizeInMB`. By default, both parameters are set to `0`, which means disabling message retention.
 
 For more information on the two parameters, refer to the [`broker.conf`](reference-configuration.md#broker) configuration file.
 
@@ -472,4 +472,4 @@ The entry log rollover period is configurable but is purely based on the entry l
 The diagram below illustrates one of the cases that the consumed storage size is larger than the given limits for backlog and retention. Messages over the retention limit are kept because other messages in the same segment are still within retention period.
 ![](/assets/retention-storage-size.svg)
 
-If you do not have any retention period and you never have much of a backlog, the upper limit for retained messages, which are acknowledged, equals the Pulsar segment rollover period + entry log rollover period + (garbage collection interval * garbage collection ratios).
\ No newline at end of file
+If you do not have any retention period and you never have much of a backlog, the upper limit for retained messages, which are acknowledged, equals the Pulsar segment rollover period + entry log rollover period + (garbage collection interval * garbage collection ratios).