Cassandra: Beyond Bigtable · Bigtable + Dynamo •LSMT / SSTables •Runtime “column” (cell)...

©2013 DataStax Confidential. Do not distribute without consent.

Jonathan Ellis

Cassandra: Beyond Bigtable

CTO, DataStax

Five years of Cassandra

Jul-09 May-10 Feb-11 Dec-11 Oct-12 Jul-13

0.1 0.3 0.6 0.7 1.0 1.2...

2.0

DSE

Jul-08

Bigtable + Dynamo

Bigtable + Dynamo•LSMT / SSTables


•Runtime “column” (cell) definition



•Schema-agnostic



•Schema-agnostic

•Size-tiered compaction



•Schema-agnostic


•Gossip-based cluster status + failure detection



•Schema-agnostic



•Hinted handoff



•Schema-agnostic



•Hinted handoff•Read repair



•Schema-agnostic




•Anti-entropy repair



•Schema-agnostic




•Anti-entropy repair•Eventually consistent

... with some differences

... with some differences•SuperColumns

... with some differences•SuperColumns•Indexes

... with some differences•SuperColumns•Indexes

•Timestamp-based conflict resolutionhttp://www.datastax.com/dev/blog/why-cassandra-doesnt-need-vector-clocks

http://www.datastax.com/dev/blog/why-cassandra-doesnt-need-vector-clocks

http://www.datastax.com/dev/blog/why-cassandra-doesnt-need-vector-clocks

Bigtable-inspired API list<ColumnOrSuperColumn> get_slice( 1:required binary key, 2:required ColumnParent column_parent, 3:required SlicePredicate predicate, 4:required ConsistencyLevel consistency_level)

Two years ago

•CQL: native protocol, prepared statements•Triggers

•Entity groups

•Smarter range queries enabling Hive predicate push-down

•Blue sky: streaming / CEP•Ease Of Use

User defined typesCREATE TYPE address ( street text, city text, zip_code int, phones set<text>)

CREATE TABLE users ( id uuid PRIMARY KEY, name text, addresses map<text, address>)

SELECT id, name, addresses.city, addresses.phones FROM users;

id | name | addresses.city | addresses.phones--------------------+----------------+-------------------------- 63bf691f | jbellis | Austin | {'512-4567', '512-9999'}

Collection indexingCREATE TABLE songs (

id uuid PRIMARY KEY, artist text, album text, title text, data blob, tags set<text>);

CREATE INDEX song_tags_idx ON songs(tags);

SELECT * FROM songs WHERE 'blues' IN tags;

id | album | artist | tags | title----------+---------------+-------------------+-----------------------+------------------ 5027b27e | Country Blues | Lightnin' Hopkins | {'acoustic', 'blues'} | Worrying My Mind

Cassandra is a...•Partitioned row store with extensions•Typed document database

•Object database

•?

SELECT * FROM usersWHERE username = ’jbellis’

[empty resultset]

INSERT INTO users (...)VALUES (’jbellis’, ...)

Session 1SELECT * FROM usersWHERE username = ’jbellis’

[empty resultset]

INSERT INTO users (...)VALUES (’jbellis’, ...)

Session 2

Paxos / CAS

Prepare / promise

Leader Replica

Replica

Replica

Leader Replica

Replica

Replica

Propose / accept

Leader Replica

Replica

Replica

Leader Replica

Replica

Replica

Read / results

Leader Replica

Replica

Replica

Leader Replica

Replica

Replica

Commit / acknowledge

Leader Replica

Replica

Replica

Leader Replica

Replica

Replica

Paxos stateCREATE TABLE paxos ( row_key blob, cf_id UUID, in_progress_ballot timeuuid, proposal_ballot timeuuid, proposal blob, most_recent_commit_at timeuuid, most_recent_commit blob, PRIMARY KEY (row_key, cf_id))

Implications•4 round trips vs 1 for normal updates•Paxos state is durable

•Linearizable consistency with no leader election or failover

•ConsistencyLevel.SERIAL

•http://www.datastax.com/dev/blog/lightweight-transactions-in-cassandra-2-0

http://www.datastax.com/dev/blog/lightweight-transactions-in-cassandra-2-0




UPDATE USERS SET email = ’[email protected]’, ...WHERE username = ’jbellis’IF email = ’[email protected]’;

INSERT INTO USERS (username, email, ...)VALUES (‘jbellis’, ‘[email protected]’, ... )IF NOT EXISTS;

Syntax

mailto:[email protected]






TriggersCREATE TRIGGER <name> ON <table>USING <classname>;

Trigger implementationclass MyTrigger implements ITrigger{ public Collection<RowMutation> augment (ByteBuffer key, ColumnFamily update) { ... }}

Atomicity?

Batches

CoordinatorNode

RedReplica

YellowReplica

BlueReplica

BatchlogNode

Batches

CoordinatorNode

RedReplica

YellowReplica

BlueReplica

BatchlogNode

X

Off-HeapNot managed by GC

Java Process

On-HeapManaged by GC

On-Heap/Off-Heap

Read path (per sstable)

Bloomfilter

Memory

Disk


Bloomfilter

Memory

Disk

Partitionkey cache


Bloomfilter

Memory

Disk

Partitionkey cache

Partitionsummary

0X...0X...0X...


Bloomfilter

Memory

Disk0X...0X...0X...0X...

Partitionindex

Partitionkey cache

Partitionsummary

0X...0X...0X...


Bloomfilter

Memory

Disk0X...0X...0X...0X...

Partitionindex

Compressionoffsets

Partitionkey cache

Partitionsummary

0X...0X...0X...


Bloomfilter

Memory

Disk0X...0X...0X...0X...

PartitionindexData

Compressionoffsets

Partitionkey cache

Partitionsummary

0X...0X...0X...

Off heap in 2.0Partition key bloom filter1-2GB per billion partitions

Bloomfilter

Memory

Disk0X...0X...0X...0X...

PartitionindexData

Compressionoffsets

Partitionkey cache

Partitionsummary

0X...0X...0X...

Off heap in 2.0Compression metadata~1-3GB per TB compressed

Bloomfilter

Memory

Disk0X...0X...0X...0X...

PartitionindexData

Compressionoffsets

Partitionkey cache

Partitionsummary

0X...0X...0X...

Off heap in 2.0Partition index summary(depends on rows per partition)

Bloomfilter

Memory

Disk0X...0X...0X...0X...

PartitionindexData

Compressionoffsets

Partitionkey cache

Partitionsummary

0X...0X...0X...

Compaction•Size-tiered•Leveled

•Others?

Size-tiered compaction

Leveled compaction

L0

L1

L2

L3

L4

L5

Sad leveled compaction

L0

L1

L2

L3

L4

L5

STCS in L0

L0

L1

L2

L3

L4

L5

HLL and compaction

Data-aware compaction?•Append-only workloads

•No compaction necessary in trivial case; still needed for clustered scans

•Append-mostly workloads?•Bounded window for out-of-order updates

Rapid Read Protection

NONE

Typical reads

Client Coordinator

40%busy

90%busy

30%busy

A failure

Client Coordinator

40%busy

90%busy

30%busy

A failure

Client Coordinator

40%busy

90%busy

30%busyX

A failure

Client Coordinator

40%busy

90%busy

30%busyXtimeout

Failure with read protection

Client Coordinator

40%busy

90%busy

30%busy


Client Coordinator

40%busy

90%busy

30%busyX


Client Coordinator

40%busy

90%busy

30%busyXsuccess

Latency (mid-compaction)

More-efficient repair

Tombstones!DELETE FROM usersWHERE username = 'jbellis'

Coordinator Replica

Replica

Replica

jbellis

jbellis

jbellis

When can we purge?•gc_grace_seconds

Pain points

Pain points•Easy to write a query that is O(N) in the number of tombstones•Tombstones must be read-repaired


•Clumsy hammer•tombstone_warn_threshold: 1000

•tombstone_failure_threshold: 100000


•Clumsy hammer•tombstone_warn_threshold: 1000

•tombstone_failure_threshold: 100000

•http://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets

http://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets




Cassandra: Beyond Bigtable · Bigtable + Dynamo •LSMT / SSTables •Runtime “column” (cell)...

Documents

Transcript of Cassandra: Beyond Bigtable · Bigtable + Dynamo •LSMT / SSTables •Runtime “column” (cell)...