You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/08/09 08:36:49 UTC

[jira] [Commented] (TS-2123) Different value of max_entries_per_buffer in client/host cause log dropped silently

    [ https://issues.apache.org/jira/browse/TS-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734456#comment-13734456 ] 

ASF subversion and git services commented on TS-2123:
-----------------------------------------------------

Commit 3c49b11ed3ab7c436db408af43be253f96c02ce4 in branch refs/heads/master from [~yunkai]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=3c49b11 ]

TS-2123: Remove useless max_entries_per_buffer option

When the configurable value of max_entries_per_buffer in LogHost is
smaller that LogClient, it'll lead to log dropped silently.

Actually, after we fix https://issues.apache.org/jira/browse/TS-2122 issue,
the max_entries_per_buffer option is unnecessary now.

Let's remove it to avoid traps caused by it.

Signed-off-by: Yunkai Zhang <qi...@taobao.com>

                
> Different value of max_entries_per_buffer in client/host cause log dropped silently
> -----------------------------------------------------------------------------------
>
>                 Key: TS-2123
>                 URL: https://issues.apache.org/jira/browse/TS-2123
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Yunkai Zhang
>         Attachments: 0001-TS-2123-Remove-useless-max_entries_per_buffer-option.patch
>
>
> When the configurable value of *max_entries_per_buffer* in LogHost is smaller that LogClient, it'll lead to log dropped silently.
> Actually, after we fix https://issues.apache.org/jira/browse/TS-2122 issue, the *max_entries_per_buffer* is unnecessary now.
> Let's remove it to avoid traps caused by it.

--
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