agsha opened a new pull request #582: URL: https://github.com/apache/logging-log4j2/pull/582
https://issues.apache.org/jira/browse/LOG4J2-3162 In the documentation of RollingFileAppender > immediateFlush boolean When set to true - the default, each write will be followed by a flush. > This will guarantee the data is written to disk but could impact performance. > Flushing after every write is only useful when using this appender with synchronous loggers. > Asynchronous loggers and appenders will automatically flush at the end of a batch of events, > even if immediateFlush is set to false. This also guarantees the data is written to disk but is more efficient. > This is misleading. The appender does not really guarantee that the data is written to disk . > All it does is call the underlying OutputStream.flush()method, > which does not guaratee that data is written to disk. It only guaratees that the data is handed over to the operating system > This is misleading. The appender does not really `guarantee that the data is written to disk` . All it does is [call](https://github.com/agsha/logging-log4j2/blob/1d56dac20d0827300a49a8cd9f0324185451757e/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/OutputStreamManager.java#L264) the underlying [OutputStream.flush()](https://docs.oracle.com/javase/7/docs/api/java/io/OutputStream.html#flush()) method, which does not guaratee that data is written to disk. It only guaratees that the data is handed over to the operating system -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
