You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2013/12/19 03:14:07 UTC

[jira] [Created] (CASSANDRA-6508) counters++ coalesce counter mutations with the same partition key

Aleksey Yeschenko created CASSANDRA-6508:
--------------------------------------------

             Summary: counters++ coalesce counter mutations with the same partition key
                 Key: CASSANDRA-6508
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6508
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Aleksey Yeschenko
            Assignee: Aleksey Yeschenko


CASSANDRA-6504 counter caching helps with hot counter cells, but doesn't really help when we have a hot counter partition and different cells within being updated simultaneously by different clients (the striped locks are partition-level, not cell-level).

To improve performance in this scenario, we could coalesce the mutations in COUNTER_MUTATION stage if they share the same partition key + target cf, and apply them together, sharing a single lock.

If beneficial, this can go into 2.1.x or 3.0, doesn't have to be 2.1.0.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)