I don't think Cassandra will complain if the cassandra/data/<keyspace> directory exists when you create <keyspace>, so you can just create your symlinks first and move on. Don't have to do the start C*, create keyspace, stop C*, move directory dance.
Other than that, I would probably just directly mount my volumes into the cassandra/data/<keyspace> directories directly instead of using symlinks, but if you're probably fine with symlinks if you really prefer. -- Sylvain On Tue, Jan 7, 2014 at 4:05 PM, Robert Wille <rwi...@fold3.com> wrote: > 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/<keyspace> to the other volume, create a symlink in its > place, restart the node. > > Is there a better way? > > Robert > > From: Tupshin Harper <tups...@tupshin.com> > Reply-To: <user@cassandra.apache.org> > Date: Tuesday, January 7, 2014 at 6:07 AM > To: <user@cassandra.apache.org> > Subject: 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" <rwi...@fold3.com> 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 thing possible or advisable? >> >
