cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8754) Required consistency level
Date Fri, 06 Feb 2015 21:14:36 GMT


Chris Lohfink commented on CASSANDRA-8754:

I could see:

# just create a Counter per CL type in CFMetrics that we can increment on read/writes.  An
AtomicLong increment isn't much overhead.
# could throw it in the topK partitions profiler (then also rename nodetool command from topkpartitions
to profile). like CASSANDRA-7974.  Would only add overhead when people are interested then.

> Required consistency level
> --------------------------
>                 Key: CASSANDRA-8754
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Ryan Svihla
>              Labels: ponies
> Idea is to prevent a query based on a consistency level not being met. For example we
can specify that all queries should be at least CL LOCAL_QUORUM.
> Lots of users struggle with getting all their dev teams on board with consistency levels
and all the ramifications. The normal solution for this has traditionally to build a service
in front of Cassandra that the entire dev team accesses. However, this has proven challenging
for some organizations to do correctly, and I think an easier approach would be to require
a given consistency level as a matter of enforced policy in the database. 
> I'm open for where this belongs. The most flexible approach is at a table level, however
I'm concerned this is potentially error prone and labor intensive. It could be a table attribute
similar to compaction strategy.
> The simplest administratively is a cluster level, in say the cassandra.yaml
> The middle ground is at they keyspace level, the only downside I could foresee is keyspace
explosion to fit involved minimum schemes. It could be a keyspace attribute such as replication

This message was sent by Atlassian JIRA

View raw message