I don't know how Kafka's rollover algorithm is implemented, but this is
common behavior for other logging frameworks. You would need a separate
watcher/scheduled thread to rollover a log file, even if no events were
coming in. Logback (and probably log4j, by the same author) dispenses with
the watcher thread. Instead, it checks each message as it comes in and
decides whether the message should belong in a new file. If it should, a
rollover of the old file is triggered and the message is deposited in the
new file. But no rollover will occur until a message that belongs in a new
file arrives.


On Fri, Apr 26, 2013 at 9:52 AM, Jason Rosenberg <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB