Skip to content

Commit 6b6afd5

Browse files
kbatuigasDeflaimun
authored andcommitted
Start section for tombstone retention
1 parent db23c5e commit 6b6afd5

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

modules/manage/pages/cluster-maintenance/compaction-settings.adoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,13 @@ Compaction policy may be applied to a cluster or to an individual topic. If both
2626
* `compact`: This triggers only cleanup of messages with multiple versions. A message that represents the only version for a given key is not deleted.
2727
* `compact,delete`: This combines both policies, deleting messages exceeding the retention period while compacting multiple versions of messages.
2828

29+
== Tombstone marker removal
30+
31+
When all messages for a given key are deleted, the topic partition keeps one message, called a tombstone, that contains the key, and a null value. A tombstone indicates to clients that the messages have been deleted. How long Redpanda keeps these tombstones depends on the topic cleanup policy:
32+
33+
* For topics with a `compact,delete` policy, Redpanda deletes the tombstones when a topic reaches its retention limits.
34+
* For topics with a `compact` policy, Redpanda deletes the tombstones based on the specified tombstone retention policy. This retention policy is set with the `delete.retention.ms` topic configuration property.
35+
2936
== Compaction policy settings
3037

3138
The various cleanup policy settings rely on proper tuning of a cluster's compaction and retention policy options. The applicable settings are:

0 commit comments

Comments
 (0)