cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Evans <eev...@rackspace.com>
Subject Re: TimeUUID Partitioning
Date Tue, 22 Dec 2009 19:55:50 GMT
On Tue, 2009-12-22 at 21:32 +0200, Richard Grossman wrote:
> Don't understand your last statement "(though so does date-based
> strings and OrderPreservingPartioner)."
> What do you mean that using TimeUUID provide a better distribution
> when using OrderPreservingPartioner. Or there is no effect if using
> OrderPreservingPartioner 

I mean that if you are using a namespace that is based on some date/time
range, and you partition that up into smaller date/time ranges, and then
store time series data, your data will be written to the node that
corresponds to the date/time, and not to any of the others.

Imagine that you have 5 nodes and they are partitioned:

A -> 2009
B -> 2010
C -> 2011
D -> 2012
E -> 2013

Any writes occurring between now and Jan 1, 2010 will go to node A, at
which point all writes will go to node B for the 365 days that follow,
and so on.

-- 
Eric Evans
eevans@rackspace.com


Mime
View raw message