-
Bug
-
Resolution: Done
-
Undefined
-
2.5.0.GA
- [DOC] Description of message deletion in case of compact policy
- There are several misleading expressions in the descriptions of message deletion in the case of compact policy(1)
- "Retention Point" line in "Figure 3. Log Retention Point and Compaction Point"
- I don't know what the "Retention Point" line in this figure is. If this means time-based or size-based log retention limits by delete policy, there should be nothing left side of this line. And it is also easy to mistake it for the "log.cleaner.delete.retention.ms" period that subsequently describes. To be precise, there is a delay of "log.segment.delete.delay.ms (default 60000)" between the decision to delete segments and the actual deletion of the segments, but this is probably not relevant here.
- The compact and deletion policies description, and the tombstone topic are too close and easily mistaken as related.
- The tombstones will be deleted by the log cleaner after "log.cleaner.delete.retention.ms". This can be done with compact policy (no need for the delete policy).
- I suggest that the description of the combination of Compact and Deletion policies be moved to the end of this section, and it should have no relation to tombstone.
- "Retention Point" line in "Figure 3. Log Retention Point and Compaction Point"
- is related to
-
ENTMQST-5200 [DOC] log.cleaner.enable doesn't work for log.cleanup.policy=delete topics
- Closed