[ https://issues.apache.org/jira/browse/CASSANDRA-14355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992599#comment-16992599 ]
Benedict Elliott Smith commented on CASSANDRA-14355: ---------------------------------------------------- This looks like the known issues with repair, which has been partially addressed in both CASSANDRA-14096 and CASSANDRA-15202. The best solution to this problem until then is to repair smaller ranges at a time, or to upgrade to a version with CASSANDRA-14096 (CASSANDRA-15202 won't be released for a while, though it could easily be back ported, and might justifiably be considered for that). > Memory leak > ----------- > > Key: CASSANDRA-14355 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14355 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core > Environment: Debian Jessie, OpenJDK 1.8.0_151 > Reporter: Eric Evans > Priority: Normal > Fix For: 3.11.x > > Attachments: 01_Screenshot from 2018-04-04 14-24-00.png, > 02_Screenshot from 2018-04-04 14-28-33.png, 03_Screenshot from 2018-04-04 > 14-24-50.png, LongGC_Dominator-Tree.png, LongGC_Histogram.png, > LongGC_Problem-Suspect-1_FastThreadLocalThread.png, LongGC_nodetool_info.txt > > > We're seeing regular, frequent {{OutOfMemoryError}} exceptions. Similar to > CASSANDRA-13754, an analysis of the heap dumps shows the heap consumed by the > {{threadLocals}} member of the instances of > {{io.netty.util.concurrent.FastThreadLocalThread}}. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org