You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2016/01/07 20:41:39 UTC
[jira] [Created] (CASSANDRA-10981) Consider striping view locks by
key and cfid
Tyler Hobbs created CASSANDRA-10981:
---------------------------------------
Summary: Consider striping view locks by key and cfid
Key: CASSANDRA-10981
URL: https://issues.apache.org/jira/browse/CASSANDRA-10981
Project: Cassandra
Issue Type: Improvement
Components: Coordination
Reporter: Tyler Hobbs
Assignee: Tyler Hobbs
We use a striped lock to protect updates to tables with materialized views, and the lock is currently striped by the partition key of the {{Mutation}}. This causes concurrent updates to separate tables with the same partition key to contend for the same lock, resulting in one or more of the mutations being rescheduled on the {{MUTATION}} threadpool (potentially becoming an asynchronous operation instead a synchronous operations, from the perspective of local internal modifications).
Since it's probably fairly common to use the same partition key across multiple tables, I suggest that we add the cfid of the affected table to the lock striping, and acquire one lock per affected table (with the same rescheduling-under-contention behavior).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)