FWIW, we've had good luck changing the mtime. No problems found.
On Mon, Apr 6, 2015 at 4:37 PM, Todd Palino wrote:
> I answered this in IRC, but the issue is that retention depends on the
> modification time of the log segments on disk. When you copy a partition
> from one broker to another, th
I answered this in IRC, but the issue is that retention depends on the
modification time of the log segments on disk. When you copy a partition
from one broker to another, the mtime of the log segments on the new broker
will be now. That means the retention clock starts over again. This means
that
I can't find any, but does anyone know of any bugs in 0.8.1.1 that would
cause new brokers added to an existing cluster to ignore the per-topic
configuration for retention?
I had a 8 node cluster with a topic with per topic retention set
like: Configs:retention.ms=540. I attempted to add 2 mor
