Currently, we don't support -1 as TTL. However, you can put an arbitrarily
large value there. The implication is that if you data keeps growing,
eventually the broker runs out of storage and will shut itself down.
Another problem is that currently we keep the file handle of each log
segment open. So, at some point, the broker will run out of file handles.
On Fri, Oct 26, 2012 at 9:09 PM, Otis Gospodnetic <
[EMAIL PROTECTED]> wrote:
> Kafka can remove messages after some TTL.
> Can one set a TTL like -1 that effectively keeps messages forever? If so,
> does that have any negative effect on performance, scalability, or
> Performance Monitoring for Solr / ElasticSearch / HBase -