Anonymitaet commented on code in PR #412:
URL: https://github.com/apache/pulsar-site/pull/412#discussion_r1128935530


##########
docs/cookbooks-retention-expiry.md:
##########
@@ -473,3 +479,6 @@ The diagram below illustrates one of the cases that the 
consumed storage size is
 ![](/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).
+
+[backlogquotacheckintervalinseconds]: 
https://pulsar.apache.org/reference/#/next/config/reference-configuration-broker?id=backlogquotacheckintervalinseconds
+[precisetimebasedbacklogquotacheck]: 
https://pulsar.apache.org/reference/#/next/config/reference-configuration-broker?id=precisetimebasedbacklogquotacheck

Review Comment:
   [This 
comment](https://github.com/apache/pulsar-site/pull/412#discussion_r1113751246) 
was left two weeks ago. The reason for my suggestion (as a temporary 
workaround) at that time was:
   
   For example, if we want to publish a new next code release (2.12.0) with 
docs, the whole 2.12.x doc set is copied from `master`. If we use 
`xxx/next/xxx` in links, then the links in the old doc set will always point to 
the latest Reference site, which is incorrect.
   
    < < < < < < < < < < < < < < < <
   
   But now you can write it as `[precisetimebasedbacklogquotacheck]: 
https://pulsar.apache.org/reference/#/@pulsar:version_origin@/config/reference-configuration-broker?id=precisetimebasedbacklogquotacheck`
 since https://github.com/apache/pulsar-site/pull/456 was merged yesterday.
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to