You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While restructuring the "Appenders" page we should explain the meaning of the immediateFlush option.
Looking at #2023, #2025 and other discussions, users often think that immediateFlush forces the OS to write the data to the underlying storage device.
That is not true, immediateFlush only flushes the Java buffers to the OS and due to the atomicity of the UNIX read()/write() calls this is usually enough for the users: if the appender logs to a pipe, the receiver should get messages up to PIPE_BUF atomically. For files and symbolic links there is no limit and operations should always be atomic.
As agreed in the site structure document, revamp the
Appenders
page such that*Manager
classes, how to handle restart2.x
module/feature deprecation #19502.x
, port tomain
The text was updated successfully, but these errors were encountered: