On Tue, Jun 9, 2015 at 6:32 AM, Anton Koshevoy wrote:
> - /etc/init.d/cassandra restart
>
Cassandra reads and makes live any files it finds in its data directory. If
you write to the keyspace and flush, is it flushing the new file in the
directory you've put your sstable in?
Permissions?
=Rob
Hi,
Not sure why this isn't working. Some thoughts, just in case:
- Have you check the files rights / owner ?
- Have you tried copying files after directory creation through your "cqlsh
-f schema" step ?
- Have you tried without setting tokens manually ?
- Are you sure to put the right sstables a
Ok, new sequence:
….
- rm -rf /db/cassandra/cr/data0*/system/*
- /etc/init.d/cassandra start
- cqlsh -f schema(here is the schema for cr_production keyspace only)
- /etc/init.d/cassandra restart
I see the new keyspace, but it’s empty:
cqlsh> describe keyspaces;
system_traces cr_production syst
On Mon, Jun 8, 2015 at 2:52 PM, Sanjay Baronia <
sanjay.baro...@triliodata.com> wrote:
> Yes, you shouldn’t delete the system directory. Next steps are
> …reconfigure the test cluster with new IP addresses, clear the gossiping
> information and then boot the test cluster.
>
If you don't delete t
a...@gmail.com]
Sent: Monday, June 8, 2015 4:42 PM
To: user@cassandra.apache.org
Subject: Re: Restoring all cluster from snapshots
Rob, thanks for the answer.
I just follow instruction from
http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_snapshot_restore_new_cluster.html
If not
I think you just have to do a "DESC KEYSPACE mykeyspace;" from one node of
the production cluster then copy the output and import it in your dev
cluster using "cqlsh -f output.cql".
Take care at the start of the output you might want to change DC names, RF
or strategy.
Also, if you don't want to
Rob, thanks for the answer.
I just follow instruction from
http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_snapshot_restore_new_cluster.html
If not to remove system table data, the test cluster starts interfering to a
production cluster. How Can I avoid this situation?
On
On Mon, Jun 8, 2015 at 6:22 AM, Anton Koshevoy wrote:
> - sudo rm -rf /db/cassandra/cr/data0*/system/*
>
This removes the schema. You can't load SSTables for column families which
don't exist.
=Rob
