You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2016/12/12 14:37:58 UTC

[jira] [Created] (CASSANDRA-13033) Thread local pools never cleaned up

Robert Stupp created CASSANDRA-13033:
----------------------------------------

             Summary: Thread local pools never cleaned up
                 Key: CASSANDRA-13033
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13033
             Project: Cassandra
          Issue Type: Bug
            Reporter: Robert Stupp
            Assignee: Robert Stupp
             Fix For: 3.0.x


Netty 4.x uses {{(Fast)ThreadLocal}} instances to provide a pool of (direct) buffers per thread ({{io.netty.buffer.PooledByteBufAllocator.PoolThreadLocalCache}}. However, these per-thread pools need to be cleaned up when a thread terminates ({{FastThreadLocal.removeAll()}}) - which is missing.

Although the possibility that such per-thread pools ever _need_ to be cleaned up, since we rarely terminate threads, it still may actually happen and manifest in a late and hard to detect out-of-memory situation. One possibility to raise such a scenario is to regularly stop and restart the native protocol service.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)