Just to clarify, do you mean you are using the RollingFileAppender in production, or the naming convention for DailyRollingFileAppender is required by your production systems?
On Thu, Jun 2, 2016 at 10:49 AM, Andrew Otto <o...@wikimedia.org> wrote: > +1, this is what Wikimedia uses in production. > > On Thu, Jun 2, 2016 at 10:38 AM, Tauzell, Dave < > dave.tauz...@surescripts.com > > wrote: > > > I haven't started using this in production but this is how I will likely > > setup the logging as it is easier to manage. > > > > -Dave > > > > -----Original Message----- > > From: Dustin Cote [mailto:dus...@confluent.io] > > Sent: Thursday, June 02, 2016 9:33 AM > > To: users@kafka.apache.org; d...@kafka.apache.org > > Subject: Changing default logger to RollingFileAppender (KAFKA-2394) > > > > Hi all, > > > > I'm looking at changing the Kafka default logging setup to use the > > RollingFileAppender instead of the DailyRollingFileAppender in an effort > to > > accomplish two goals: > > 1) Avoid filling up users' disks if the log files grow unexpectedly > > 2) Move off the admittedly unreliable DailyRollingFileAppender > > > > I wanted to know if the community has any feedback around this before > > moving forward. The main drawback with going to the RollingFileAppender > is > > that the log file names will no longer have timestamps, but instead be of > > the form server.log, server.log.1, etc. What users are depending on the > > file name convention and would need to rollback the log4j configuration > > should the default change in a later version? What sort of feedback can > > those users provide to help us document this the right way? > > > > Thanks, > > > > -- > > Dustin Cote > > confluent.io > > This e-mail and any files transmitted with it are confidential, may > > contain sensitive information, and are intended solely for the use of the > > individual or entity to whom they are addressed. If you have received > this > > e-mail in error, please notify the sender by reply e-mail immediately and > > destroy all copies of the e-mail and any attachments. > > > -- Dustin Cote confluent.io
