[
https://issues.apache.org/jira/browse/CASSANDRA-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162565#comment-16162565
]
Markus Dlugi commented on CASSANDRA-13754:
------------------------------------------
[~urandom], I think it might still be the same issue. The threads you mentioned
are all created by the {{SEPWorker}} as well, as you can also see in your
screenshot where your {{FastThreadLocalThread}} has a reference to an instance
of that class. Now I'm not sure whether the actual content of your
{{ThreadLocalMap}} s is the same as in my heap dump - in my case, the maps
mostly held instances of {{BTree$Builder}} , which then had references to many
{{byte[]}} arrays. Maybe you can check if this is the case for you as well?
Other than that, you could also try and see if the patches created by [~snazy]
alleviate your 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
>
>
> 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]
