cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Goffinet (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-404) SSTable write lock not releasing
Date Tue, 01 Sep 2009 04:09:32 GMT


Chris Goffinet updated CASSANDRA-404:

    Attachment: stack.log.gz

Our stack trace from the running node in question.

> SSTable write lock not releasing
> --------------------------------
>                 Key: CASSANDRA-404
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.4
>            Reporter: Chris Goffinet
>         Attachments: stack.log.gz
> Today we saw a node lock up when trying to serve reads. Current investigation shows that
some threads are trying to acquire a ssTable_.lock(). This means that somehow Cassandra has
gotten into a state with a write lock that has not been released (blocking read locks). Thrift
connections started piling up after this occurred. We also are seeing a race condition with
ConcurrentLinkedHashMap using appendToTail. 
> We are currently investigating the ssTable lock. We could remove the ConcurrentLinkedHashMap
for now until that's resolved.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message