cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Reopened] (CASSANDRA-13754) BTree.Builder memory leak
Date Mon, 11 Sep 2017 22:14:00 GMT


Eric Evans reopened CASSANDRA-13754:

I apologize for chiming in here so late, but I'm not sure this addresses what I was seeing.
 In my dumps, all of the heap is tied up in the {{ThreadLocalMap}} s of instances of {{FastThreadLocalThread}}
for _Native-Transport-Requests_, _RequestResponseStage_, _ReadStage_, etc; I think what I
was seeing is different than [~markusdlugi].

See the attached screenshot of the dominator tree view in MemoryAnalyzer.

I can make a dump available, but be warned, it is 12G in size.

> BTree.Builder memory leak
> -------------------------
>                 Key: CASSANDRA-13754
>                 URL:
>             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
> 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|;a=commit;h=cecbe17e3eafc052acc13950494f7dddf026aa54]
fixes the issue.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message