Keyspaces on different volumes

I¹d like to have my keyspaces on different volumes, so that some can be on SSD and others on spinning disk. Is such a thing possible or advisable?

Re: Keyspaces on different volumes

That is a fine option and can make perfect sense if you have keyspaces with very different runtime characteristics. -Tupshin On Jan 7, 2014 7:30 AM, "Robert Wille" wrote: > I’d like to have my keyspaces on different volumes, so that some can be on > SSD and others on spinning disk. Is such a thi

Re: massive spikes in read latency

/** * Verbs it's okay to drop if the request has been queued longer than the request timeout. These * all correspond to client requests or something triggered by them; we don't want to * drop internal messages like bootstrap or repair notifications. */ public static fin

nodetool cleanup / TTL

This has not reached a consensus in #cassandra in the past. Does `nodetool cleanup` also remove data that has expired from a TTL?

Re: Keyspaces on different volumes

The obvious (but painful) way to do that would be to create the keyspace, and then repeat the following for each node: shut down the node, move cassandra/data/ to the other volume, create a symlink in its place, restart the node. Is there a better way? Robert From: Tupshin Harper Reply-To: D

Re: nodetool cleanup / TTL

On Tue, Jan 7, 2014 at 7:49 AM, Chris Burroughs wrote: > This has not reached a consensus in #cassandra in the past. Does > `nodetool cleanup` also remove data that has expired from a TTL? No, cleanup only removes rows that the node is not a replica for. -- Tyler Hobbs DataStax

Re: delay/stall processing reads

Thanks Lee, I put these in place on one of the three servers, and while doing so I noticed in the logs on the other servers that there were many errors from our weekly nodetool repair of this form: On Thu, Jan 2, 2014 at 9:34 PM, Lee Mighdoll wrote: > Well from what I see in system.log it does

Re: delay/stall processing reads

Apologies I sent that prior email too soon. I see exceptions in the log during nodetool repair like these: ERROR [AntiEntropySessions:1] 2014-01-06 21:46:45,339 RepairSession.java (line 278) [repair #179e84f0-775f-11e3-9c6a-538c9374b226] session completed with the following error org.apache.cassand

Re: nodetool cleanup / TTL

On 01/07/2014 01:38 PM, Tyler Hobbs wrote: On Tue, Jan 7, 2014 at 7:49 AM, Chris Burroughs wrote: This has not reached a consensus in #cassandra in the past. Does `nodetool cleanup` also remove data that has expired from a TTL? No, cleanup only removes rows that the node is not a replica fo