cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alain RODRIGUEZ <arodr...@gmail.com>
Subject Re: Restoring all cluster from snapshots
Date Tue, 09 Jun 2015 18:24:41 GMT
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 at the right place (if # nodes
prod or RF are different from production) ?
- Is trying to use sstableloader an option you want to consider ?

Good luck,

C*heers,

Alain

2015-06-09 15:32 GMT+02:00 Anton Koshevoy <nowarry@gmail.com>:

>  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  system
>
>  cqlsh> use cr_production ;
>  cqlsh:cr_production> select * from cr_production.url_cs ;
>
>  id | ct | d_id
>  ----------------+---------+-----------
>
> (0 rows)
>
>
>  =================
>  Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address       Load       Tokens  Owns    Host ID
>         Rack
> UN  10.40.231.3   74.35 KB   256     ?
> 7fc4f832-9d98-4bfd-81fb-0c361bff487d  RACK01
> UN  10.40.231.31  86.46 KB   256     ?
> 782d450d-50d5-4738-a654-bf7398557842  RACK01
>
> Note: Non-system keyspaces don't have the same replication settings,
> effective ownership information is meaningless
>
> then I tried:
>
>  - nodetool refresh -- cr_production url_cs
>
>  with the same result.
>
>
> On June 9, 2015 at 1:29:36 AM, Robert Coli (rcoli@eventbrite.com) wrote:
>
>   On Mon, Jun 8, 2015 at 2:52 PM, Sanjay Baronia <
> sanjay.baronia@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 the system directory, you run the risk of the test
> cluster nodes joining the source cluster.
>
> Just start a single node on the new cluster, empty, and create the schema
> on it.
>
> Then do the rest of the process.
>
> =Rob
>
>
>

Mime
View raw message