DOC-1378: Compaction robustness

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

@@ -61,6 +61,22 @@ Where:
 | xref:reference:cluster-properties.adoc#log_compaction_interval_ms[`log_compaction_interval_ms`]
 | Cluster
 | Compaction frequency in milliseconds.
+
+| xref:reference:cluster-properties.adoc#max_compaction_lag_ms[`max_compaction_lag_ms`]
+| Cluster
+| The maximum amount of time in milliseconds that a message remains ineligible for compaction. Use to guarantee the maximum delay between the time a message is written and the time the message becomes eligible for compaction. This setting is useful for ensuring that messages are compacted within a predictable timeframe.
+
+| xref:reference:cluster-properties.adoc#min_compaction_lag_ms[`min_compaction_lag_ms`]
+| Cluster
+| The minimum time in milliseconds that a message remains uncompacted in the log. Use to guarantee the minimum length of time that must pass after a message is written before it could be compacted. For example, to provide a lower bound on how long each message will remain in the (uncompacted) head.
+
+| xref:reference:properties/topic-properties.adoc#max.compaction.lag.ms[`max.compaction.lag.ms`]
+| Topic
+| The maximum amount of time in milliseconds that a message remains ineligible for compaction. Use to guarantee the maximum delay between the time a message is written and the time the message becomes eligible for compaction.
+
+| xref:reference:properties/topic-properties.adoc#min.compaction.lag.ms[`min.compaction.lag.ms`]
+| Topic
+| The minimum time in milliseconds that a message remains uncompacted in the log. Use to guarantee the minimum length of time that must pass after a message is written before it could be compacted. For example, to provide a lower bound on how long each message will remain in the (uncompacted) head.
 |===
 
 Redpanda runs a scan every `log_compaction_interval_ms`. During each scan:

modules/reference/pages/properties/cluster-properties.adoc

@@ -3705,6 +3705,26 @@ Maximum compacted segment size after consolidation.
 
 ---
 
+=== max_compaction_lag_ms
+
+For a compacted topic, the maximum time a message remains ineligible for compaction. The topic property `max.compaction.lag.ms` overrides this property.
+
+*Unit:* milliseconds
+
+*Requires restart:* No
+
+*Visibility:* `user`
+
+*Type:* integer
+
+*Accepted values:* [`1`, `9223372036854`]
+
+*Default:* `9223372036854`
+
+*Related topics*: xref:reference:properties/topic-properties.adoc#max.compaction.lag.ms[`max.compaction.lag.ms`]
+
+---
+
 === max_concurrent_producer_ids
 
 Maximum number of active producer sessions. When the threshold is passed, Redpanda terminates old sessions. When an idle producer corresponding to the terminated session wakes up and produces, its message batches are rejected, and an out of order sequence error is emitted. Consumers don't affect this setting.
@@ -3950,7 +3970,29 @@ The minimum ratio between the number of bytes in dirty segments and the total nu
 
 ---
 
-// tag::minimum_topic_replications[]
+=== min_compaction_lag_ms
+
+The minimum amount of time (in ms) that a log segment must remain unaltered before it can be compacted in a compact topic.
+
+*Unit:* milliseconds
+
+*Requires restart:* No
+
+*Visibility:* `user`
+
+*Type:* integer
+
+*Accepted values:* [`0`, `9223372036854`]
+
+*Default:* `0`
+
+*Related topics*:
+
+- xref:reference:properties/topic-properties.adoc#min.compaction.lag.ms[`min.compaction.lag.ms`]
+
+---
+
+[[minimum_topic_replications]]
 === minimum_topic_replications
 
 ifdef::env-cloud[]