Description
Currently there is this setting:
log.retention.hours
introduce:
log.retention.size
Semantic would be, either size is reached or time is reached, oldest messages will be deleted.
This does not break back-ward compatibility and would make the system robust under scenarios where message size is not deterministic over time.