cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nimi Wariboko Jr. (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-12882) Deadlock in MemtableAllocator
Date Fri, 04 Nov 2016 21:57:58 GMT
Nimi Wariboko Jr. created CASSANDRA-12882:
---------------------------------------------

             Summary: Deadlock in MemtableAllocator
                 Key: CASSANDRA-12882
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12882
             Project: Cassandra
          Issue Type: Bug
         Environment: Ubuntu 14.40
Cassandra 3.5
            Reporter: Nimi Wariboko Jr.
             Fix For: 3.5
         Attachments: cassandra.yaml, threaddump.txt

I'm seeing an issue where a node will eventually lock up and their thread pools - I looked
into jstack, and a lot of threads are stuck in the Memtable Allocator

{code}
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
	at org.apache.cassandra.utils.concurrent.WaitQueue$AbstractSignal.awaitUninterruptibly(WaitQueue.java:279)
	at org.apache.cassandra.utils.memory.MemtableAllocator$SubAllocator.allocate(MemtableAllocator.java:198)
	at org.apache.cassandra.utils.memory.SlabAllocator.allocate(SlabAllocator.java:89)
	at org.apache.cassandra.utils.memory.ContextAllocator.allocate(ContextAllocator.java:57)
	at org.apache.cassandra.utils.memory.ContextAllocator.clone(ContextAllocator.java:47)
	at org.apache.cassandra.utils.memory.MemtableBufferAllocator.clone(MemtableBufferAllocator.java:41)
{code}

I looked into the code, and its not immediately apparent to me what thread might hold the
relevant lock.



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

Mime
View raw message