[
https://issues.apache.org/jira/browse/CASSANDRA-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904373#action_12904373
]
Stu Hood commented on CASSANDRA-1293:
-------------------------------------
How much of a benefit do we get from the row cache being write-through? It
would be really nice not having to lock it... or maybe making the locking and
write-throughness an option, via CASSANDRA-1158. It would also be easier to
manage cache sizes in terms of bytes if we didn't need to deal with mutations
to the row cache.
> add locking around row cache accesses
> -------------------------------------
>
> Key: CASSANDRA-1293
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1293
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
>
> CASSANDRA-1267 means we need to lock around removeDeleted on the row cache
> entry and the write path where we merge in new columns (otherwise there can
> be a race where we incorrectly continue to remove a column, that has been
> updated by the writer thread to be newly relevant)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
