The danger of using a size based rollover (unless you set the size and
log rollover to be fairly high) is that in case of problems, the actual
cause of the problem might get rolled off the end by the time you get to
it (kafka can be very chatty in some kinds of failure cases).  That is
probably the biggest reason for a date-rolling log...

On the other hand, the date-rolling can leave a lot of cruft around if
you do not have a cleaner process running on a periodic basis...

Dave DeMaagd
[EMAIL PROTECTED] | 818 262 7958

([EMAIL PROTECTED] - Mon, Jul 01, 2013 at 11:26:24AM -0700)

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