You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Susan Hinrichs (JIRA)" <ji...@apache.org> on 2015/09/14 18:36:46 UTC
[jira] [Assigned] (TS-3898) Connection to the origin can allocate
1MB of iobuffers
[ https://issues.apache.org/jira/browse/TS-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Susan Hinrichs reassigned TS-3898:
----------------------------------
Assignee: Susan Hinrichs (was: kang li)
> Connection to the origin can allocate 1MB of iobuffers
> ------------------------------------------------------
>
> Key: TS-3898
> URL: https://issues.apache.org/jira/browse/TS-3898
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Affects Versions: 5.3.0, 6.0.0
> Reporter: Bryan Call
> Assignee: Susan Hinrichs
> Labels: yahoo
> Fix For: 6.1.0
>
>
> When connecting to an origin there can be 1MB of iobuffers allocated. This happens under TLS and non-TLS. Seems like it happens when the origin doesn't supply a content-length. More investigation is needed.
> Configuration:
> {code}
> [bcall@homer trafficserver]$ tail -1 /usr/local/etc/trafficserver/remap.config
> map / https://www.flickr.com
> {code}
> Client:
> {code}
> [bcall@homer trafficserver]$ curl -D - -k https://127.0.0.1:4443/
> [bcall@homer trafficserver]$ sudo kill -SIGUSR1 $(pidof traffic_server){code}
> Server:
> {code}
> allocated | in-use | type size | free list name
> --------------------|--------------------|------------|----------------------------------
> 1048576 | 0 | 32768 | memory/ioBufAllocator[8]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)