THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
It seems that naming LogCleaner is somewhat misleading and LogComparator is more appropriate one. So LogCleaner and related classes/methods/configs should be renamed to Comparator instead of Cleaner
Public Interfaces
log.cleaner.enable will be deprecated and eventually, it will be removed from the configuration. Going forward if log.cleanup.policy is set to compact then cleaner will be enabled implicitly.
Following old configuration will be deprecated and new renamed configuration will be introduced.
| Existing configuration | New configuration | log.cleaner.enable | log.compactor.enable|
|---|---|---|---|
| log.cleaner.backoff.ms | log.compactor.backoff.ms | ||
| log.cleaner.dedupe.buffer.size | log.compactor.dedupe.buffer.size | ||
| log.cleaner.delete.retention.ms | log.compactor.delete.retention.ms | ||
| log.cleaner.io.buffer.load.factor | log.compactor.io.buffer.load.factor | ||
| log.cleaner.io.buffer.size | log.compactor.io.buffer.size | ||
| log.cleaner.io.max.bytes.per.second | log.compactor.io.max.bytes.per.second | ||
| log.cleaner.min.cleanable.ratio | log.compactor.min.cleanable.ratio | ||
| log.cleaner.min.compaction.lag.ms | log.compactor.min.compaction.lag.ms | ||
| log.cleaner.threads | log.compactor.threads |
...