We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Currently we configure the buffer of the access log like this:
access_log {* http.access_log *} main buffer=32768 flush=3;
According to Nginx's doc:
The buffer size must not exceed the size of an atomic write to a disk file
http://nginx.org/en/docs/http/ngx_http_log_module.html
And for Linux, the default atomic write size is PIPE_BUF (4096), see man 7 pipe.
PIPE_BUF
man 7 pipe
Therefore, the default size is too large to be safe.
The text was updated successfully, but these errors were encountered:
+1 A log buffer that is too small is not good, 4096 is more appropriate.
Sorry, something went wrong.
On the other hand, is flush=1 better? Since the log buffer is lowered, the flush time should also be lowered.
flush=1
#1570
Successfully merging a pull request may close this issue.
Currently we configure the buffer of the access log like this:
According to Nginx's doc:
http://nginx.org/en/docs/http/ngx_http_log_module.html
And for Linux, the default atomic write size is
PIPE_BUF
(4096), seeman 7 pipe
.Therefore, the default size is too large to be safe.
The text was updated successfully, but these errors were encountered: