merlimat closed pull request #2049: Issue 1416: Docs about garbage collection 
are inaccurate/lacking
URL: https://github.com/apache/incubator-pulsar/pull/2049
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/site/docs/latest/admin/GeoReplication.md 
b/site/docs/latest/admin/GeoReplication.md
index 4acc658c27..7abc25a14f 100644
--- a/site/docs/latest/admin/GeoReplication.md
+++ b/site/docs/latest/admin/GeoReplication.md
@@ -137,6 +137,8 @@ Each cluster reports its own local stats, including 
incoming and outgoing replic
 
 Given that global topics exist in multiple regions, it's not possible to 
directly delete a global topic. Instead, you should rely on automatic topic 
garbage collection.
 
-In Pulsar, a topic is automatically deleted when it's no longer used, that is 
to say, when no producers or consumers are connected *and* there are no 
subscriptions. For global topics, each region will use a fault-tolerant 
mechanism to decide when it's safe to delete the topic locally.
+In Pulsar, a topic is automatically deleted when it's no longer used, that is 
to say, when no producers or consumers are connected *and* there are no 
subscriptions *and* no more messages are kept for retention. For global topics, 
each region will use a fault-tolerant mechanism to decide when it's safe to 
delete the topic locally.
+
+You can explicitly disable topic garbage collection by setting 
`brokerDeleteInactiveTopicsEnabled` to `false` in your [broker 
configuration](../../reference/Configuration/#Broker-ckhlfn).
 
 To delete a global topic, close all producers and consumers on the topic and 
delete all its local subscriptions in every replication cluster. When Pulsar 
determines that no valid subscription for the topic remains across the system, 
it will garbage collect the topic.


 

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to