[
https://issues.apache.org/jira/browse/TS-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716625#comment-13716625
]
Leif Hedstrom commented on TS-777:
----------------------------------
So, there might be a few issues here.
1) We don't consistently use the configurations from records.config
2) Do we need to assure that the various log configurations actually work
together properly. E.g. increasing the log-buffer, without increasing the
max-line-size could cause us to trigger the bug in TS-2063. In fact, it might
be that this bug is completely dependant on TS-2063.
> Increasing logbuffer size makes us "drop" log entries
> -----------------------------------------------------
>
> Key: TS-777
> URL: https://issues.apache.org/jira/browse/TS-777
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Affects Versions: 2.1.8
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Labels: A
> Fix For: 3.5.1
>
>
> Setting proxy.config.log.log_buffer_size higher than somewhere around 24KB
> makes us start losing log entries. This is bad, since increasing this setting
> could be a way to increase performance for busy systems. I've for now set the
> defaults to 16KB, which seems to be stable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
