cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-8161) Spin loop when streaming tries to acquire SSTable references
Date Mon, 27 Oct 2014 23:32:34 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yuki Morishita resolved CASSANDRA-8161.
---------------------------------------
    Resolution: Duplicate

I saw several "Restore replica count"s and one "Bootstrap" at the same time, and I thought
there was something going on SSTable.acquireReference.

But it turns out I was looking at the old version of the code that matches thread dump, and
I believe it is now fixed in CASSANDRA-7073 in 2.0.8.
In their C* version, SSTable references could have screwed up and led to the loop.

> Spin loop when streaming tries to acquire SSTable references
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-8161
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8161
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Yuki Morishita
>            Priority: Minor
>
> When streaming files, stream session tries to acquire references on SSTables to stream.
When there are multiple sessions trying to stream same part of SSTables, they sometimes wait
a *very* long time (nealy dead lock) on trying to acquire references.
> I think we need something we've done to AtomicSortedColulmns in CASSANDRA-7546 to reduce
contention.



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

Mime
View raw message