title: Kafka retention AFTER initial consuming
body: <p>I have a Kafka cluster with one consumer, which is processing TB's of data every day. Once a message is consumed and committed, it can be deleted immediately (or after a retention of few minutes).</p>
  
  <p>It looks like the <code>log.retention.bytes</code> and <code>log.retention.hours</code> configurations count from the message creation. Which is not good for me.</p>
  
  <p>In case where the consumer is down for maintenance/incident, I want to keep the data until it comes back online. If I happen to run out of space, I want to refuse accepting new data from the producers, and NOT delete data that wasn't consumed yet (so the <code>log.retention.bytes</code> doesn't help me).</p>
  
  <p>Any ideas?</p>