AWS msk documentation change
Summary
Removed three log compaction/retention configuration parameters from documentation.
Security assessment
Removal of non-security-related configuration details. No impact on security documentation.
Diff
diff --git a/msk/latest/developerguide/msk-configuration-express-read-write.md b/msk/latest/developerguide/msk-configuration-express-read-write.md index 1792e586b..8b2104cb3 100644 --- a//msk/latest/developerguide/msk-configuration-express-read-write.md +++ b//msk/latest/developerguide/msk-configuration-express-read-write.md @@ -36,3 +35,0 @@ leader.imbalance.per.broker.percentage | The ratio of leader imbalance allowed -log.cleaner.delete.retention.ms | The amount of time to retain delete tombstone markers for log compacted topics. This setting also gives a bound on the time in which a consumer must complete a read if they begin from offset 0 to ensure that they get a valid snapshot of the final stage. Else, delete tombstones might be collected before they complete their scan. | 86400000 (24 * 60 * 60 * 1000 ms, that is, 1 day), Apache Kafka Default -log.cleaner.min.compaction.lag.ms | The minimum time a message will remain uncompacted in the log. This setting is only applicable for logs that are being compacted. | 0, Apache Kafka Default -log.cleaner.max.compaction.lag.ms | The maximum time a message will remain ineligible for compaction in the log. This setting is only applicable for logs that are being compacted. This configuration would be bounded in the range of [7 days, Long.Max]. | 9223372036854775807, Apache Kafka Default