[ 
https://issues.apache.org/jira/browse/CASSANDRA-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Stupp resolved CASSANDRA-13754.
--------------------------------------
    Resolution: Fixed

[~urandom], it's not about the {{BTree.Builder}} instances, it's about what's 
kept referenced by those - and that is the bunch of {{HeapByteBuffer}} 
instances, as reported by [~markusdlugi] and fixed by the patch for this 
ticket. The screenshot you attached, matches the fixed issue. Therefore, I 
recommend to try the patch or a build from the recent 3.11/trunk branches and 
test again. Going go resolve this issue. If it's really something else that's 
causing the issue, I'd prefer to open another ticket, because there is already 
something committed for this ticket that addresses a very particular issue.

> BTree.Builder memory leak
> -------------------------
>
>                 Key: CASSANDRA-13754
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13754
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Cassandra 3.11.0, Netty 4.0.44.Final, OpenJDK 8u141-b15
>            Reporter: Eric Evans
>            Assignee: Robert Stupp
>             Fix For: 3.11.1
>
>         Attachments: Screenshot from 2017-09-11 16-54-43.png, Screenshot from 
> 2017-09-13 10-39-58.png
>
>
> After a chronic bout of {{OutOfMemoryError}} in our development environment, 
> a heap analysis is showing that more than 10G of our 12G heaps are consumed 
> by the {{threadLocals}} members (instances of {{java.lang.ThreadLocalMap}}) 
> of various {{io.netty.util.concurrent.FastThreadLocalThread}} instances.  
> Reverting 
> [cecbe17|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=cecbe17e3eafc052acc13950494f7dddf026aa54]
>  fixes the issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to