You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2014/05/12 20:47:15 UTC
[jira] [Comment Edited] (TS-2796) Leaking CacheVConnections
[ https://issues.apache.org/jira/browse/TS-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995439#comment-13995439 ]
Bryan Call edited comment on TS-2796 at 5/12/14 6:45 PM:
---------------------------------------------------------
Memory diff of a LinkedIn vs Yahoo production host:
The values are LinkedIn host memory value - Yahoo host memory value and print it if is was non-zero.
{code}
name allocated in_use type_size allocated(MB)
memory/ArenaBlock 786432 -54272 1024 0
memory/FetchSMAllocator 36864 0 288 0
memory/RamCacheCLFUSEntry 364953600 364946400 96 348
memory/RamCacheLRUEntry -9601024 -9126016 64 -9
memory/cacheRemoveCont -6144 0 48 0
memory/cacheVConnection -9977856 -4804256 928 -9
memory/dnsBufAllocator -135424 0 33856 0
memory/evacuationBlock -737280 -737856 96 0
memory/evacuationKey -6144 0 48 0
memory/eventAllocator -73728 584832 96 0
memory/hdrStrHeap -26476544 -5216256 4096 -25
memory/httpClientSessionAlloca -48039936 -45016704 656 -45
memory/httpSMAllocator -135473152 -105433456 9728 -129
memory/httpServerSessionAlloca 143360 382816 224 0
memory/ioAllocator -18800640 -17246160 240 -17
memory/ioBlockAllocator -9543680 -8705600 64 -9
memory/ioBufAllocator[0] -131072 0 128 0
memory/ioBufAllocator[10] 264241152 -626130944 131072 252
memory/ioBufAllocator[11] 6526337024 -537133056 262144 6224
memory/ioBufAllocator[12] 4093640704 -545783808 524288 3904
memory/ioBufAllocator[13] -805306368 -642777088 1048576 -768
memory/ioBufAllocator[2] -65536 0 512 0
memory/ioBufAllocator[3] -131072 0 1024 0
memory/ioBufAllocator[4] -2359296 -8192 2048 -2
memory/ioBufAllocator[5] -585105408 -542396416 4096 -558
memory/ioBufAllocator[6] 6397624320 6433579008 8192 6101
memory/ioBufAllocator[7] 14313586688 14380695552 16384 13650
memory/ioBufAllocator[8] 9016705024 4105961472 32768 8599
memory/ioBufAllocator[9] 3965714432 -621150208 65536 3782
memory/ioDataAllocator 77807616 78438960 48 74
memory/mutexAllocator -6225920 -5812000 80 -5
memory/netVCAllocator -17719296 -15882048 672 -16
memory/openDirEntry -1822720 -1109280 160 -1
memory/sslNetVCAllocator -43683840 -37772640 720 -41
{code}
was (Author: bcall):
Memory diff of a LinkedIn vs Yahoo production host:
{code}
name allocated in_use type_size allocated(MB)
memory/ArenaBlock 786432 -54272 1024 0
memory/FetchSMAllocator 36864 0 288 0
memory/RamCacheCLFUSEntry 364953600 364946400 96 348
memory/RamCacheLRUEntry -9601024 -9126016 64 -9
memory/cacheRemoveCont -6144 0 48 0
memory/cacheVConnection -9977856 -4804256 928 -9
memory/dnsBufAllocator -135424 0 33856 0
memory/evacuationBlock -737280 -737856 96 0
memory/evacuationKey -6144 0 48 0
memory/eventAllocator -73728 584832 96 0
memory/hdrStrHeap -26476544 -5216256 4096 -25
memory/httpClientSessionAlloca -48039936 -45016704 656 -45
memory/httpSMAllocator -135473152 -105433456 9728 -129
memory/httpServerSessionAlloca 143360 382816 224 0
memory/ioAllocator -18800640 -17246160 240 -17
memory/ioBlockAllocator -9543680 -8705600 64 -9
memory/ioBufAllocator[0] -131072 0 128 0
memory/ioBufAllocator[10] 264241152 -626130944 131072 252
memory/ioBufAllocator[11] 6526337024 -537133056 262144 6224
memory/ioBufAllocator[12] 4093640704 -545783808 524288 3904
memory/ioBufAllocator[13] -805306368 -642777088 1048576 -768
memory/ioBufAllocator[2] -65536 0 512 0
memory/ioBufAllocator[3] -131072 0 1024 0
memory/ioBufAllocator[4] -2359296 -8192 2048 -2
memory/ioBufAllocator[5] -585105408 -542396416 4096 -558
memory/ioBufAllocator[6] 6397624320 6433579008 8192 6101
memory/ioBufAllocator[7] 14313586688 14380695552 16384 13650
memory/ioBufAllocator[8] 9016705024 4105961472 32768 8599
memory/ioBufAllocator[9] 3965714432 -621150208 65536 3782
memory/ioDataAllocator 77807616 78438960 48 74
memory/mutexAllocator -6225920 -5812000 80 -5
memory/netVCAllocator -17719296 -15882048 672 -16
memory/openDirEntry -1822720 -1109280 160 -1
memory/sslNetVCAllocator -43683840 -37772640 720 -41
{code}
> Leaking CacheVConnections
> -------------------------
>
> Key: TS-2796
> URL: https://issues.apache.org/jira/browse/TS-2796
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Affects Versions: 4.0.2, 4.2.1, 5.0.0
> Reporter: Brian Geffon
> Labels: yahoo
> Fix For: 5.0.0
>
>
> It appears there is a memory leak in 4.0.x, 4.2.x, and master leaking CacheVConnections resulting in IOBufAllocator leaking also, here is an example:
> allocated | in-use | type size | free list name
> 67108864 | 0 | 2097152 | memory/ioBufAllocator[14]
> 67108864 | 19922944 | 1048576 | memory/ioBufAllocator[13]
> 4798283776 | 14155776 | 524288 | memory/ioBufAllocator[12]
> 7281311744 | 98304000 | 262144 | memory/ioBufAllocator[11]
> 1115684864 | 148242432 | 131072 | memory/ioBufAllocator[10]
> 4974444544 | 379977728 | 65536 | memory/ioBufAllocator[9]
> 9902751744 | 5223546880 | 32768 | memory/ioBufAllocator[8]
> 14762901504 | 14762311680 | 16384 | memory/ioBufAllocator[7]
> 6558056448 | 6557859840 | 8192 | memory/ioBufAllocator[6]
> 41418752 | 30502912 | 4096 | memory/ioBufAllocator[5]
> 524288 | 0 | 2048 | memory/ioBufAllocator[4]
> 0 | 0 | 1024 | memory/ioBufAllocator[3]
> 0 | 0 | 512 | memory/ioBufAllocator[2]
> 32768 | 0 | 256 | memory/ioBufAllocator[1]
> 0 | 0 | 128 | memory/ioBufAllocator[0]
> 2138112 | 2124192 | 928 | memory/cacheVConnection
> [~bcall] has observed this issue on 4.0.x, and we have observed this on 4.2.x.
> The code path in CacheVC that is allocating the IoBuffers is memory/IOBuffer/Cache.cc:2603; however, that's just the observable symptom the real issue here is the leaking CacheVC.
--
This message was sent by Atlassian JIRA
(v6.2#6252)