[
https://issues.apache.org/jira/browse/CASSANDRA-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439231#comment-13439231
]
Jonathan Ellis commented on CASSANDRA-4533:
-------------------------------------------
You're right, my mistake. +1
> Multithreaded cache saving can skip caches
> ------------------------------------------
>
> Key: CASSANDRA-4533
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4533
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0
> Reporter: Zhu Han
> Assignee: Yuki Morishita
> Priority: Trivial
> Fix For: 1.1.5
>
> Attachments: 4533-1.1.txt
>
>
> Cassandra flushes the key and row cache to disk periodically. It also uses a
> atomic flag in flushInProgress to enforce single cache writer at any time.
> However, the cache saving task could be submitted to CompactionManager
> concurrently, as long as the number of worker thread in CompactionManager is
> larger than 1.
> Due to the effect of above atomic flag, only one cache will be written out to
> disk. Other writer are cancelled when the flag is true.
> I observe the situation in Cassandra 1.0. If nothing is changed, the problem
> should remain in Cassandra 1.1, either.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
